Does the Tomcat5 session persistence also persist container-managed auth credentials, when the credentials were created using JBoss/JAAS integrated security?
On Wed, 2004-07-28 at 22:34, Bryan Feld wrote:
I'm using JBoss 3.2.5 with Tomcat5, and have built an application which uses container-managed authentication (using an application-policy and the DatabaseServerLoginModule).
My problem is, when I reload my web application, rather than Tomcat5 persisting and reloading the active sessions, instead it seems to freak out for users who were online at the time. When they click anything, they are redirected over and over again to the /index.jsp page until their browser redirection limit is reached.
Another app on the same server, which doesn't use container-managed authentication, seems to persist and reload sessions just fine when the webapp is restarted.
Any help would be appreciated,
Bryan
