Double serialization might cause performance issues with Weblogic
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- You might encounter performance issues in case serialization is enabled on both Liferay's and Weblogic's side, for example the following logs might suggest this problem:
<Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "694" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@5c0f63ae[GET /c/portal/layout]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace
Environment
- Liferay DXP 7.0
- Liferay DXP 7.1
- Liferay DXP 7.2
- Liferay DXP 7.3
Resolution
- Remove the line
<optimistic-serialization>true</optimistic-serialization> from the portal's WEB-INF/weblogic.xml;
- Add the line
weblogic.request.wrap.non.serializable=false to the portal-ext.properties file.
- In case serialization is required then configure it on only one side if possible
Did this article resolve your issue ?