Search Results

All Results 7008
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Unable to startup the server: NPE while loading configurations from database
legacy Troubleshooting
Issue The issue usually comes with Oracle database and having a null dictionary in the table Configuration_ for the configurationid org_apache_felix_cm_impl_DynamicBindings Due to this, Liferay fails to start,...
Workarounds for "The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit"
legacy Troubleshooting
Issue Eventually, the JSP compiler might show error messages like: The code of method _jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535 bytes limit Environment DXP 7.2 DXP 7.1 DXP 7.0...
Upgrading from Liferay DXP 7.1 to 7.2
legacy How To
This paper is a high-level overview of the effort involved in moving from Liferay DXP 7.1 to 7.2. It contains an upgrade checklist, the upgrade steps, and what to do after a successful...
Liferay DXP Feature Comparison
legacy
Each version of Liferay improves on the features and functionality of previous versions.  Since the release of Liferay Portal 6.2 EE, the Liferay platform has continued to evolve to...
DXP 7.2 Service Pack 1 (SP1) - New Improvements for Data Consistency
legacy
Liferay DXP 7.2 Service Pack 1 (SP1) includes changes that further improve data consistency within the Liferay platform. Highlights: Additional Liferay services now have Multiversion Concurrency Control (MVCC) enabled...
About automating the setup wizard
legacy How To
This article has been machine translated from its original language for your convenience. Please use discretion as this translation may include some inaccuracies. If you encounter issues with the translation, please...
MEMORY_CLUSTERED jobs are running in several nodes
legacy Troubleshooting
Issue According to traces, or any other monitoring system, MEMORY_CLUSTERED jobs are executed in more than one node. Environment Liferay DXP 7.0, 7.1, 7.2 Resolution MEMORY_CLUSTERED jobs should only run in...
Company/Instance name is reset to 'Liferay DXP' after restart
legacy Troubleshooting
Issue Having chaged the name of the main instance, it is reset to 'Liferay DXP' after restarting the portal. Neither portal-ext.properties nor Config Admin name change is preserved. Environment Liferay DXP 7.1...