RE: WAR Deployment before starting the cluster

2010-10-01 Thread Romain Petit
/2010 10:06 AM, Romain Petit wrote: > My HttpSessionBindingListener was not notified because the session > replicated were deserialized, there were no attributes binding. > > So to get notified a session is replicated on a new server you can wrap > the readObject(ObjectInputStream in) o

RE: WAR Deployment before starting the cluster

2010-10-01 Thread Romain Petit
session replicated were deserialized, there were no attributes binding. So to get notified a session is replicated on a new server you can wrap the readObject(ObjectInputStream in) or use the other session listener. Bye bye From: Romain Petit Sent: Monday, September 27, 2010 1:35 PM To

WAR Deployment before starting the cluster

2010-09-27 Thread Romain Petit
Hello, We have 2 tomcat servers in cluster with session sharing and notifyListenersOnReplication=true. The application deployed uses a HttpSessionBindingListener to be aware of the number of licenses used by a user on the 2 servers. This configuration works great when the 2 servers are