We're using JBoss 4.0.1 in a Windows 2003 environment and have a slow leak.
JBoss is installed as a service. Using the -Xloggc switch when installing the
service, we get garbage collection logs. In the course of 3-5 days, the logs
show memory can no longer be collected and maxes out at the 1gb
Thank you for your response!
Alright, I will make all the objects placed on httpSession serializable.
Coming from a commercial app server environment, we were spoiled by it's
ability to simply igore these objects on the session, not forwarding them to
other cluster member nodes.
So, if we are
forgot to mention that to deploy clustered I also included additional jar files
in the server/deployment/lib folder: jboss-cache.jar, jgroups.jar and
jboss-remoting.jar.
So, if Clustering now uses jgroups, does that mean it is not using a lick of
ejb under the covers? If our application has no
I've set up clustering in JBoss 4.0.1 per the documents and we have tested
successfully in staging. The day we first tried this in production, a memory
leak occurred and crashed the system within 8 minutes ! The original release
used JDK 1.5.0_02.
I built the environment by using the "defaul
