Standard Session Last Accessed Time(Standard Session Facade.java:87) at com.icesoft.faces.webapp.xmlhttp.
Blocking Response State.remaining Millis(Blocking Response State.java:169) at com.icesoft.faces.webapp.xmlhttp.
The minimal implementation provided by the servlet classes in JSDK 2.0 manages sessions through the use of persistent cookies.
A server can build on this base to provide additional features and capabilities.
I'm on the same road, clustering liferay with terracotta, so please contact me if you'd like to collaborate.
This should be resolved in the 2.4 branch (as of revision 3923) Any nightly build past that revision, or the next 2.4 stable release will contain the fix.
For example, the Java Web Server has the ability to revert to using URL rewriting when cookies fail, and it allows session objects to be written to the server's disk as memory fills up or when the server shuts down.
(The items you place in the session need to implement the interface to take advantage of this option.) See your server's documentation for details pertaining to your server.
This decreses the builtin security, but it will get a little further down the road.
The do Filter() method will be called for each request of our application.
We will see shortly what parameters do we passed in filter.
Following small piece of code comes handy whenever you are working for a J2EE web application in JSP/Servlet/Struts/JSF or any Servlet oriented web framework. Hence we can check the session in this method and see if it is valid.
A lot of time we have to handle session errors in such applications and redirect user to particular error page. From init() method, we had generated a list of pages (urls) that were having access although the session is null.