Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.7RC1
-
Fix Version/s: 1.7
-
Component/s: None
-
Labels:None
-
Environment:portal portlet
Description
It's not reliably reproducible but, occasionally, when you do a hot redeploy of portlet war after the session has expired, causes the server to appear to hang. Reloading the browser windows when this happened resulted in emtpy portlet windows and it requires the server to be "force quit".
When it occurred, I had redeployed the .war and Liferay had successfully copied it (messages in the console indicated) and the server was trying to shutdown the component-showcase deployment. The log messages from SessionDispatcher appeared:
Log.info("Session already invalidated.");
and then it basically hung.
When it occurred, I had redeployed the .war and Liferay had successfully copied it (messages in the console indicated) and the server was trying to shutdown the component-showcase deployment. The log messages from SessionDispatcher appeared:
Log.info("Session already invalidated.");
and then it basically hung.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Run shutdown sequence only once. When re-deploying an application there's an additional shutdown call made by container, for the sessions that just expired the lock waiting for view disposals is then re-created thus blocking the re-deployment.
Show
Mircea Toma
added a comment - Run shutdown sequence only once. When re-deploying an application there's an additional shutdown call made by container, for the sessions that just expired the lock waiting for view disposals is then re-created thus blocking the re-deployment.
Assigning to Mircea