Oops, I missed something :
When you use or
the behaviour is different if the pathname/directory is absolute or relative.
If it is relative, it is stored relative to each applications temporary work
directory, and handled with each application classLoader, and it works
perfectly.
Maybe this
Hi,
I have bug https://bz.apache.org/bugzilla/show_bug.cgi?id=48007 on recent
tomcats.
To reproduce one must:
- use PersistentManager in global context.xml
- have an object in session only available through a webapp class loader
- wait for manager backgroundProcess to call PersistentManagerBase