[
http://jira.jboss.com/jira/browse/JBAS-3358?page=comments#action_12350503 ]
Javid Jamae commented on JBAS-3358:
-----------------------------------
This guy has a work around:
http://www.ethelred.org/articles/2006/10/18/persisting-http-sessions-over...
He says: "So my final workaround was to add a context.xml to each individual web app
- it goes in the WEB-INF directory - to set the Manager pathname to one including that web
app's name. I also used a relative path of ../../.. to make the session files be
written outside of the working directories that would be deleted, but avoid using a
non-portable path.
This seemed to do the trick. Phew! (As an aside, I haven't actually written a
context.xml for each web app - they are dynamically created by our build script)."
Work directory for the web app shouldn't be deleted on Context
Destroy
----------------------------------------------------------------------
Key: JBAS-3358
URL:
http://jira.jboss.com/jira/browse/JBAS-3358
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Javid Jamae
Assigned To: Anil Saldhana
Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta1
I tried enabling HTTP session persistence, but found out that the default directory that
it writes to is the work directory. Working with JBoss support, I discovered that the work
directory is deleted when the server shuts down.
Either the work directory should not be deleted, or the default directory where the
persistent HTTP sessions are serialized to a file should be changed to be in a directory
other than work (since it is being deleted).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira