Larry, Sathish,
Rebooting your web server service is a workaround. Optimizing that heap size
will reduce the frequency with which you would need to restart the web
server service. You can also turn on the incremental garbage collection
(-Xincgc) which will further enhance your jvm. This article will help you
understand this option.. It’s a random article I just found for you.
http://www.petefreitag.com/articles/gctuning/
There are loads of other resources that you can find if you search for
incremental garbage collection.. At one site not more than 2 years ago,
where I used this option, I noticed that the web servers that would fail
almost daily, would run out of memory sometimes after a week or weeks..
which is better if not good..
Joe
-----Original Message-----
From: SUBSCRIBE arslist Sathish
Sent: Thursday, October 28, 2010 3:29 AM
To: arsl...@listserv.rbugs.com ; Joe DeSouza
Cc: SUBSCRIBE arslist Sathish
Subject: Re: java error from 7.1 mid-tier on
We run into this error very frequently due to heavy mid tier user count.
Since we got just one instance of Mid tier, we got a weekly maintenance
window where it take 2-3 minutes to restart the Mid tier which bring down
the JVM.
The other options to explore monitoring tool to warn you on JVM getting
reaching a threshold, and to go for multiple mid tier instance where you can
restart JVM for each instance without any downtime of end users.
Hope this helps!!
Sathish
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
