HTTPSession Cookie Changed

[Niraj Salot]

Dear all,

We are facing some serious issue.

After accessing the application for some time , We are having timeout
issue. Although the timeout is set to 2 hours , we are seeing that
session are expired only after 15-20 Minutes.

We are using GWT , Spring. our application is deployed on JBOSS 7.0.2.
We are using the HTTPSession in server side only. We are expecting
that during each RPC , browser will send the JSESSION ID cookie with
each request. No seperate coding is done for this.

After our deeper analysis we have found that from client side the
cookie which contians the jSESSIONID is suddenly changed and when it
reaches to server , server create the issue of timeout.

One more thing... The application works fine for couple of users. The
problem only starts when we have more users connected to the
application. Have check memory and CPU stuff. They are fine. nothing
serious over there.

Any help would be greatly appreciated.

Thanks.
Niraj.

[Juan Pablo Gardella]

Are you use clusters? reverse proxy?

2011/10/26 Niraj Salot <salot...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Jens]

So far I have only seen this in clusters with session replication and a round robin load balancer (or multiple DNS entries which is basically some sort of round robin load balancing). Sometimes session replication fails and a new session is created on a cluster node. You could use sticky load balancing to reduce the chance of a lost session because of replication. 

Already searched for JBOSS issues regarding lost sessions?