Search Results

NOTE: Be sure to take a backup of your database prior to making any changes. Always test the changes in a lower environment before making changes in production. Making manual changes to the database is not recommended, and should be carefully assessed based on your own business needs and...

Issue The following errors are encountered when the user accesses the portal, which increases the log size. ERROR [https-jsse-nio-0.0.0.0-8443-exec-29][DynamicIncludeUtil:81] java.io.IOException: Unable to include JSP /html/portal/dynamic_include/view.jsp java.io.IOException: Unable to...

Issue Is there a way to check the progress of an upgrade while it is still happening?  Environment Quarterly Release 2024.Q1 2023.Q4 2023.Q3 DXP 7.4 DXP 7.3 DXP 7.2 DXP 7.1 Resolution The simplest way to do this would be to tail the upgrade log, which is typically located in...

Issue When trying to perform an upgrade, the following error appears in logs: ERROR [main][DBUpgrader:70] Missing default Store Environment Quarterly Release: 2023.Q3, 2023.Q4, 2024.Q1, 2024.Q2 Liferay DXP 7.4 Resolution Check that the path specified in your file...

Issue Start up an environment with Liferay DXP 2024.Q2 and JDK 17. The following error message appears: ERROR [io.undertow.servlet.request] (ServerService Thread Pool -- 78) UT015005: Error invoking method contextDestroyed on listener class jdk.proxy10.$Proxy40:...

Issue Configuring log rotation for logs based on the size. Environment Liferay DXP 7.4 Resolution The logs can be rotated based on size by making a small adjustment in the portal-log4j.xml file. Extract portal-impl.jar from /tomcat-9.0.73/webapps/ROOT/WEB-INF/shielded-container-lib/ and...

Issue We are finding many Warns "SAX Security Manager could not be setup" in the Liferay logs. How can we resolve these messages? Environment Liferay Quarterly Release 2024 Resolution The observed behavior is a known issue addressed by LPD-20262. Please update to DXP 2024.Q2.0 Quarterly...

Issue When tailing the upgrade log in a new terminal separate from where the upgrade was initiated, the following logs indicating the completion of an upgrade may not be printed:  Completed Liferay core upgrade process in xxxxx seconds Checking to see if all upgrades are completed… done”...