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 "default" server deployment and added Clustering by adding to it jbossha-httpsession.sar, tc5-cluster-service.xml, httpha-invoker.sar jbossha.jar and cluster-service.xml files in the deploy folder and changing configuration files as documented. We are only needing the HTTPSession clustering. Do I really need all the other stuff listed above ? To get over the memory leak, I first rolled back to JDK 1.4, which seemed to slow the leak down to 1 hour instead of 8 minutes. Then I tried removing the reliance on farm deployment which had no affect. Finally I removed the clustering modules (and replaced httpha-invoker with http-invoker). That relieved the problem -- no more fast leak (although over the course of a week we will leak slowly -- perhaps thats our own application). I do believe some of our java modules that are added to httpSession are not serializable while most are. The occurance of the "not serializable" error is minimal when clustering is turned on. Has anyone else had this problem ? Any ideas ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3881644#3881644 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3881644 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
