We have two web Applications , each one is deployed on seperate websphere application server. Both of these websphere Application server is fronted by
an Apache proxy server , So request is routed from the proxy server to the websphere application server. we have proxy mapping for both the applications ,
when we open a jsp page of the 2nd aplication from the first web application in a child window through (window.open) the session of 1st web application , is getting
This is not happening when two web applications are deployed seperately on Tomcat and fronted by a apache proxy server. I think its something todo with
websphere settings .
for your information , we are using websphere 6.1 as our application server, and apache 2.2 as our proxy server
and we have the following mappings in our apache httpd.conf file
ProxyPass /firstWebApp http:/machine1:9080/firstWebApp
and the apache proxy server is running on machine1.
posted 9 years ago
after debugging this issue we found some more details about the problem , the http session is not getting killed , to confirm this we have added HttpSessionListener to verify when the session getting destroyed , but the destroy() method has never get called even after it creates a new HttpSession. So only the browser is losing its reference to that old session, and we have session timeout for 30 minutes , after this time the session destroy() method is getting called for the old session. I hope this additional information will be helpful .
I can suggest you one thing to try. By default the name of the cookie dropped is JSESSIONID. Try changing the name of the cookie for both the web apps and see if the problem goes away. It seems like the coookie names are same and opening the second webapp causes the browser to override the cookie of first web app.
posted 9 years ago
Yes your right, by changing the cookie name of the Applications we got it solved . Thanks for the reply. The JsessionId is getting overwritten every time when the 2nd web application has been launched .