Hi,

Another possible solution would be to change the session timeout value just for the Clearspace install by changing the value for session timeout in the web.xml file in the clearspace WEB-INF directory of your application server.  This timeout value would then override the global timeout value of the application server just for Clearspace sessions.

As for the the autosave properties, looking at the code it appears that autosave is enabled by default with an interval of 30 seconds so unless you have explicitly disabled autosave previously, it should already be active.  In my own testing locally, it appears that having autosave enabled with an interval less than the session timeout time does indeed keep the session open because, as you suggested, it causes action with the server.

Finally, it is my understanding that Harpo has some custom authentication code.  As such, I cannot test these possibilities with your exact implementation and so cannot give a definite answer.  I would advise that you try changing the timeout value in the Clearspace web.xml file first.  If that doesn't work, then I would advise opting for the autosave option by setting the properties you discovered (although again, it appears that these should be enabled by default).

Cheers,

Scott

Hi,

What is the session timeout value that is set in the web.xml specific to your Clearspace install?

As for the autosave, it follows the "doc-create" action so you would want to look up that action in your xwork XML configuration files.  You probably want to look at the intereceptors that are being used for the action.  Look for some special logic that is timing out the session along the interceptor stack.  For example, in the base install the stack includes the "jivelogin" interceptor which is defined as being the JiveLoginInterceptor class.

Cheers,

Scott