Search Results

All Results 6982
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Error when deserializing a session
Issue You might get an error when trying to deserialize a session, which looks similar to this: java.lang.IllegalStateException: Error deserializing Session [2522563CC05A5789E25189BD49FFB38C]...
When attempting to use a Read/Write database split configuration, the Liferay startup logging warns that Hypersonic is in use
Issue When setting up an environment that uses a read/write database split, it appears that Liferay tries to use Hypersonic (HSQL) instead of the configured database, as the startup logs note: WARN ...
Auto Upgrade in DXP 7.3 and Above
Issue Starting from Liferay 7.3, new upgrades for modules won't run automatically on startup by default. Resolution The following options are available to run the upgrades we may include in fix/service packs:...
ClassCastException in Xerces with JBoss EAP 7.3 and IBMJava
Issue When Liferay 7.3 is deployed on JBoss EAP 7.3 using IBMJava, the following exception is thrown at startup and the server fails to start: ERROR [ServerService Thread Pool --...
Groovy Script to truncate the data of UserTrackPath Table
Issue If you want to truncate the data from UserTrackPath Table Environment Liferay DXP 7.2 Resolution Below is the Groovy Script which might help to truncate the data from UserTrackPath table. import...
Upgrade to DXP 7.3 fails due to error about an already existing column
Issue When running the DB Upgrade Tool, the upgrade fails due to an error regarding a duplicate or already existing defaultvirtualHost column. (See examples of the error below) Upgrading Oracle DB Caused by:...
What Is The Property Layout.url?
Issue What is this property and how it is invoked by Liferay? layout.url=${liferay:mainPath}/portal/layout?p_l_id=${liferay:plid}&p_v_l_s_g_id=${liferay:pvlsgid} Environment Liferay DXP 7.2 Resolution layout.url defines the...
Intermittent LDAP login failures due to LDAP response read time out
Issue With large LDAP directories, user login can sometimes fail if the LDAP query takes longer than the configured read timeout (default value is 500ms)  WARN [http-bio-exec][LDAPAuth:176] Failed to bind to the LDAP...