multiple instances of jboss

[rlopez]

"rlopez" wrote:
I have two instances of jboss-tomcat running on the same machine using ServiceBindingManager. Both instances are running identical version of the same application. Everything seems fine except that when I log into one instance it invalidates my session on the second instance. I've debugged it and it seems like the session is loosing its variables. I'm at a loss at this and through seraching the forums have yet to find a similar problem

Please help!

[darranl]

"darranl" wrote:
Are you logging in to both from the same machine?

Which web browser are you using?

If Internet Explorer how are both of the windows opened?

Are you using cookies or URL rewriting?

It sounds to me as if cookies are replacing each other at the client end which is why the other one gets invalidated.

[rlopez]

"rlopez" wrote:
Thank you for your reply.

Are you logging in to both from the same machine?

Yes

Which web browser are you using?

Ive tried it with IE6 and Mozilla 1.5. The same occurs whether I acces the app locally or from a remote client.

If Internet Explorer how are both of the windows opened?

How many different ways are there? It makes no difference

Are you using cookies or URL rewriting?

Cookies

It sounds to me as if cookies are replacing each other at the client end which is why the other one gets invalidated.

Well, the thing is that I can open multiple session to the same app on the same server instance with no such problem. This only occurs if its to separate instances on the same host.

[rlopez]

"rlopez" wrote:
OK, using cookie manager in mozilla, I've verified that in fact the cookies are replacing each other since they come from the same host with same path and name.

Host: localhost
Path: /ewms
Name: JSESSIONID

Ahhh... your comment about cookies overriding and the "how are you opening the explorere windows" sparked something in my head.

It seems the cookies are overriding each other when the windows are opened as "children (File->New Window)" of the previous one rather than from the "explorer icon on the desktop"

And the reason this doesn't occur when accessing the same server instance is that the server knows it has previously issued a cookie to you and so it gives you a new one for the new request.

Thanks for the spark!