http://anonsvn.jboss.org/repos/jbossas/tags/JBPAPP_4_2_0_GA_CP06/tomcat/src/main/org/jboss/web/tomcat/service/session/
is the package where the distributed session manager code resides.
http://anonsvn.jboss.org/repos/jbossas/tags/JBPAPP_4_2_0_GA_CP06/tomcat/src/main/org/jboss/web/tomcat/service/s
I did a bit more testing, and it seems that once I shut down n1, there is some
increase in HashMap$Entry's and TreeMap$Entry's on n2. This is a test setup, so
n2 is not servicing any requests when I stop n1. So I am guessing, it might
have to do with the session being promoted from backup to act
I don't have any specific log categories, no, as without more information on
what's increasing in the heap there's not much to go on.
When n1 is shut down, n2 starts getting failover requests and starts doing
twice as much work, so memory increase is expected. Perhaps the increase would
be a bi
Thank you for your reply.
Those are our customer's servers, so I don't have a direct line to JBoss
customer support, but I might try to have a ticket opened once I have something
more concrete.
I am planning on getting a heap dump when I get the chance to reproduce this,
but I was wondering
First off, if you are using EAP you are quite likely a support customer. If so
you should open a ticket on the Customer Support Portal, where you'll get much
better support than I can provide in the half hour or so I day I spend on this
forum.
A basic debugging step is to take a heap histogram
