Rainer,
> No, the design of mod_jk is stateless w.r.t. sessions. There are only the
> obvious solutions, i.e. assuming that after some time of disabling (time
> depending on typical session use cases like 10 minutes or an hour) you stop
> the worker and thereby redirect users that still try to use the node to
> another node. They'll get an error of course and would need to relogin.
> Usually with some time of disable status you can reduce the number of
> sessions, that will need to relogin and thus be disturbed by your
> maintenance to about 5% (your mileage may vary).
> If you want to improve user experience more, you could include a
> maintenance information in your app, like "Please logout and relogin during
> the next hour because we have a maintenance scheduled starting at ...".
thank you a lot for the fast follow-up and the clarification of the
stateless architecture of mod_jk in case of session ids. I will continue
to do the obvious as you described it.
Thomas
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
