it is not very easy to "guess" a memory leak. Of course upgrading to the 
latest Resin (3.0.21) could help. But you should better consider 
profiling your application with e.g. JProfiler. You can download an 
evaluation version which is valid for 10 days.
If you are using JDK 1.5, using jconsole 
http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html could 
also help. You could at least find out which memory spaces are involved 
in the memory leak.


chuboz wrote:
> Dear IT colleagues,
> I have a resin server running on Sun Solaris 5.8 . I used memory up to 1 GB
> for my application.
> But I still have a problem because of memory leak. 
> My application using JMS memory queue and Message Driven Bean to fetch it. I
> have 4 queues and 3 type of Message Driven Bean.
> Each type of message driven bean used up to 10 instances.
> Here is my problem, 
> My resin server services around 100 thousands transactions per day. Free
> memory is decreasing every day. 
> So every week I have to restart resin in order to restore all memory. Is it
> garbage collector in resin doesn't work well? or is my JVM configuration
> wrong? 
> I'm using JVM configuration like below
> -Xss8192k -Xmn64M -Xms1024M -Xmx1024M -XX:SurvivorRatio=20
> -XX:MaxTenuringThreshold=1 -XX:MaxPermSize=32M
> Looking forward for your answer.
> Thanks.

Markus Ken Moriyama <[EMAIL PROTECTED]>
Development Director

Eastbeam Co., Ltd.
Jingumae Happy Bldg 8F, 6-19-14 Jingumae, Shibuya-ku
150-0001 Tokyo, Japan
Tel: +81 3 5766 0874
Fax: +81 3 3499 8217


resin-interest mailing list

Reply via email to