Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 1.7.1
-
Fix Version/s: None
-
Component/s: Framework
-
Labels:None
-
Environment:Liferay 5.1.2 running on apache tomcat 6.0 , mysql 5.0
Description
Hi all!
I am getting the 'User Session Expired' popUp frequently when the web application remains idle for approximately 30 minutes.
These are the details of my liferay environment:
Liferay 5.1.2 running on apache tomcat 6.0 , mysql 5.0.
I tried to set the properties of file 'portal-ext.properties' (session.timeout=60, session.timeout.warning=0, session.timeout.auto.extend=true), but i didn't have result.
I added 'emptySessionPath=true' to the server.xml, and didn't have result.
Now don't displays the 'User session expired' window, but continues to expire. And in the log file appears the following message:
ERROR [SessionDispatcher:106] java.lang.IllegalStateException: getAttributeNames: Session already invalidated
My portlets are inaccessible until I close and reopen the browser.
Can anyone help me? Does anyone have a solution to this problem?
Thank you!
I am getting the 'User Session Expired' popUp frequently when the web application remains idle for approximately 30 minutes.
These are the details of my liferay environment:
Liferay 5.1.2 running on apache tomcat 6.0 , mysql 5.0.
I tried to set the properties of file 'portal-ext.properties' (session.timeout=60, session.timeout.warning=0, session.timeout.auto.extend=true), but i didn't have result.
I added 'emptySessionPath=true' to the server.xml, and didn't have result.
Now don't displays the 'User session expired' window, but continues to expire. And in the log file appears the following message:
ERROR [SessionDispatcher:106] java.lang.IllegalStateException: getAttributeNames: Session already invalidated
My portlets are inaccessible until I close and reopen the browser.
Can anyone help me? Does anyone have a solution to this problem?
Thank you!
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.
Show
Ken Fyten
added a comment - Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.
I'm sorry you're encountering difficulties with your ICEfaces portlets. Posting specifically on our forums and/or taking advantage of our support offerings are some ways to help avoid this pain in the future. We do have numerous clients successfully using ICEfaces with Liferay so it's possible this is simply a configuration issue of some kind.
Although the "Session Expired" dialog generally indicates a true session expiry situation, it has been known to popup for other reasons. Interaction with portal contains can be a bit complicated as Ajax requests do not go through the portal container (it would cause a full page refresh) so there are some things, like session activity, that have to be handled differently. In addition, Liferay has it's own Ajax code with interacts with the session from the client side but does not interact directly with ICEfaces.
Here are my initial suggestions:
1) According to your entry in the JIRA, you are working with ICEfaces 1.7.1. The first thing I would do is upgrade to 1.8.2 and see if the problem persists. A lot of changes have been made between the version you are using and our latest release. If you are using Ajax Push in your portlets, we strongly recommend that you also deploy the Push Server which is a simple .war file you can just copy to Tomcat's webapps directory.
2) If the problem still manifests with the newer ICEfaces version then please provide a simple test case that shows the problem and attach it to this JIRA so that we can analyze and fix as required.
3) If, after upgrading to 1.8.2, you have a test case that still shows the problem, there is a feature that we've recently added that may be of help. It's noted in this JIRA: http://jira.icefaces.org/browse/ICE-4785.
This feature/API allows an app to touch the session from either the client side or the server/app side which allows the application developer to keep the session active in the way they choose. More details are provided in the documentation or you can solicit help on the forums if you get to this point.