Posted by jpereza on Dec 03, 2010; 9:55am
URL: https://discuss.orbeon.com/Problem-in-a-non-persistant-session-environment-tp3069014p3070849.html

Hi Erik,

I've made a quick-and-dirty fix for this problem: implement my own ServletContextListener and stop the database instances when the servlet context is destroyed.

But this is not a good solution, the database is stopping twice!

I think that the good solution would be something like this:

* The EXistServlet shouldn't stop the database by itself
* It should be responsibility of eXist's users to stop the database,
** So, Orbeon should stop the eXist database AFTER making its own cleaning job, thus via a ServletContextListener.

I've seen you are using your own copy of eXist (exist-1_2_6_orbeon_20090702.jar), so you will be able to make this modifications by yourself.

Hope this help.

Best regards,
jpereza