Here is what I did to reproduce this:
Deploy clusterjsp.war example on a cluster with 2 nodes with the following
modifications:
- add distributable directive into WEB-INF/web.xml
- remove sun-web.cml
- put random varlues into the session, about 5k worth.
After a while, the session gets lost with the following error:
[#|2011-10-10T20:36:09.789-0400|WARNING|glassfish3.1.1|org.shoal.ha.cache.command.load_request|_ThreadID=33;_ThreadName=Thread-2;|LoadRequestCommand
timed out while waiting for result java.util.concurrent.TimeoutException|#]
[quote=mk111283]Looking into this. I have tested the replication module by
having 16 threads trying to write and read data with asyncreplication set to
false. In that scenario, I DID NOT see any data loss or degradation in
performance. I am about to test the replication module using JMeter and
cluster.jsp app. Will post the response in the next couple of days. Thanks,
--Mahesh On 10/09/2011 05:34 AM, forums_at_java.net wrote: > I am observing the
exact same problem in the GF 3.1.1 release > > The app is incredibly slow and
losing sessions. If 'Enable > Availability' is > off, everything works gread.
> > I also have <distributable/> in the web.xml > > Thanks > > > -- > >
[Message sent by forum member 'lprimak'] > > View Post:
http://forums.java.net/node/778666 > >[/quote]
--
[Message sent by forum member 'lprimak']
View Post: http://forums.java.net/node/778666