Thanx to Antonio, Joerg and Javier for your hints. But it seems as if the cause of our problem depends not to the versions of our jdk or tomcats . We also have problems with newer versions of tomcat on our other servers. Meanwhile we guess that the problems maybe relate to the mod_jk2 module of our front apache 2 server.
First guess: We have one Apache 2 server configured with modjk2 to load balance to 4 servers in the backend. The last time we lost session attributes our jkstatus overview showed one of our backend servers in error state. It seems that the ajp connector of this server was down. So requests of users with active sessions on this broken server will be routed by modjk to another server. So far we thought that the session is invalide for the tomcat which is relevant next. Is it possible that the session is still valid for this new tomcat? It seems so because the session is valid cocoon action gives true. So the generator is executed but cannot access the relevant session attributes and fails. Second guess: Once we restart our frontend apache 2 (not graceful) the session attributes are lost again. After restart it is possible that one user with an active session on server X is now routed to server Y by modjk2 because apache doesn't know the active server for each user. So far we thought that the session is invalide for server Y but it seems that it's not the case because our first cocoon sitemap pipe uses the session is valid action. It seems that this action gives true and the generator is executed but cannot access session attributes and failes. Can anybody give further information about apache 2, modjk and tomcats session handling in error cases? We need your help please. Thanx to all, Markus. -----Ursprüngliche Nachricht----- Von: Antonio Gallardo [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 28. Oktober 2003 00:31 An: [EMAIL PROTECTED] Betreff: Re: Session attributes lost Markus Heussen dijo: > Hi all, > > Our environment: > > * Win2K > * first Apache Tomcat/4.1.18 with JDK 1.3.1_07-b02 Can you upgrade to Tomcat 4.1.27? Best Regards, Antonio Gallardo > * Apache 2.0.44 in Front of the Tomcat an with mod_jk2 2.0.43 running > for load balancing > * JBoss 3.2.1 with a separate JDK 1.3.1_07 included a Tomcat 4.1.24 Here too: Tomcat 4.1.27? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
