You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Murali Vivekanandan <mv...@cisco.com> on 2003/04/09 02:14:27 UTC

Memory problem with tomcat323 or Solaris

Hi,

Our application on Tomcat 3.23, jdk 1.3 on Solaris  is leaking memory. The 
process size
crosses 1GB in  about 10 days time.

Probing heap with OptimizeIT did not reveal any java object leaks.
Over an interval of an hour the process size increases by about 1 to 5 MB where
as the total heap size (which we print out from within our app) does not
increase at all.

So we suspected that leak is in the native layer.  We don't use JNI
ourselves, the only JNI use in our application is the OCI driver library.

We have reviewed our code multiple times to make sure there are no unclosed
resources.

We do allocate and de allocate a lot of objects to display our search 
result pages.

Can you CC your replies to mvivekan@cisco.com as I am not subcribed to the 
list currently?

Any thoughts?

Thanks,
Murali


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Re: Memory problem with tomcat323 or Solaris

Posted by "G. Wade Johnson" <wa...@abbnm.com>.
If I remember the Oracle docs correctly, there was a note about resource
leaks if you weren't real careful to make certain you close every
connection/statement/result set that you use.

I don't know if that could explain all of the leak, but it is something
to check.

G. Wade

Murali Vivekanandan wrote:
> 
> Hi,
> 
> Our application on Tomcat 3.23, jdk 1.3 on Solaris  is leaking memory. The
> process size
> crosses 1GB in  about 10 days time.
> 
> Probing heap with OptimizeIT did not reveal any java object leaks.
> Over an interval of an hour the process size increases by about 1 to 5 MB where
> as the total heap size (which we print out from within our app) does not
> increase at all.
> 
> So we suspected that leak is in the native layer.  We don't use JNI
> ourselves, the only JNI use in our application is the OCI driver library.
> 
> We have reviewed our code multiple times to make sure there are no unclosed
> resources.
> 
> We do allocate and de allocate a lot of objects to display our search
> result pages.
> 
> Can you CC your replies to mvivekan@cisco.com as I am not subcribed to the
> list currently?
> 
> Any thoughts?
> 
> Thanks,
> Murali
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org