ure globally
PersistentManager.
It would be enough for us to have an option to disable
Storebase.processExpires(), but it may be somewhat ugly...
cu
Pascal Rigaux.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional comm
On 04/12/2024 18:09, Mark Thomas wrote:
The Manager/Store component can't easily determine if it is being configured
from the global, host or context level context.xml file.
The root cause here is configuration error - configuring multiple web
applications to use the same file for session pers
should be mentionned more clearly in the documentation? Maybe
display a warning log for absolute pathname/directory in global context.xml?
cu,
Pascal R.
On 03/12/2024 16:36, Pascal Rigaux wrote:
Hi,
I have bug https://bz.apache.org/bugzilla/show_bug.cgi?id=48007 on recent
tomcats.
To
Hi,
On some applications we have:
- quite low number of users most of the time
- high number of users twice a year
These applications store quite a lot of information in session.
To cope with the surge of users, we would need to:
- either increase mx (Java max memory)
- or use short session time
se, as you suggested, the application should not depend on such big
sessions. That's the real solution to avoid any issues!
cu
Pascal Rigaux.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands,
