Hi,
Is it normal for Glassfish to assign a new session-id to a client if its
session is moved to another server?
We run a Glassfish-Cluster with 2 servers, and when we take Server-1 down
which has a client connected the following happens:
[code]
DEBUG 2010-11-12 12:01:12,774 -
http://javaserver:5826/palme/servlet;jsessionid=fbe1c94ef4acd1e2acae6beac31f.0
DEBUG 2010-11-12 12:01:12,778 - Request-URL:
/palme/servlet;jsessionid=fbe1c94ef4acd1e2acae6beac31f.0
DEBUG 2010-11-12 12:01:12,778 - Session-ID: fbf07c93203b593829ead600c65b
isNew:true
[/code]
The client is properly redirected to server2 where this log is from, and uses
its old Session-ID (fbe1c94ef4acd1e2acae6beac31f.0), however when I ask the
session about its ID and wether its new I get a "fresh" session-id and the
session says it just has been created.
HttpSession session = request.getSession();
Logger.getLogger("PalmeLogger").debug("Session-ID: "+session.getId()+"
isNew:"+session.isNew());
Does this mean session-replication isn't working? If so, any ideas what could
be the problem?
Thank you in advance, Clemens Eisserer
--
[Message sent by forum member 'linuxhippy']
View Post: http://forums.java.net/node/717332