Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / August 2007

Tip: Looking for answers? Try searching our database.

Tomcat Memory Issue

Thread view: 
Sagar - 20 Aug 2007 21:34 GMT
We are running a web service on Tomcat 6.0 with JDK 1.5.0_12. on a
2003 Windows Server with 2GB memory.

In our load test we nioticed the memory usage for Tomcat gradually
increases. Once it reaches 2 GB, Tomcat crashes.  The same
application, which is written in AION language, was tested on our PC's
and it doesn't take more than 25MB of memory.

Also, when we were running the load test, the total of Heap and Non
Heap Memory was never more than 35GB. Also validated GC process was
regularly started.

JVM Committed Memory was the only one which was identical to Physical
Memory Usage.Our assumption was Tomcat Committed Memory will be equal
to the total of Heap and Non Heap memory. Can someone please explain
if there is any process used by Tomcat which is eating up all the
memory?

Any help to fix this issue would be great as we are stuck at this
point.

Thanks,
C.K
Manish Pandit - 20 Aug 2007 22:02 GMT
> We are running a web service on Tomcat 6.0 with JDK 1.5.0_12. on a
> 2003 Windows Server with 2GB memory.
[quoted text clipped - 19 lines]
> Thanks,
> C.K

What kind of webservice is it - stateless/stateful/composite ? Is it
transactional ? Is it hitting multiple resources and not releasing
them for some reason?

-cheers,
Manish
Arne Vajhøj - 21 Aug 2007 00:43 GMT
> We are running a web service on Tomcat 6.0 with JDK 1.5.0_12. on a
> 2003 Windows Server with 2GB memory.
>
> In our load test we nioticed the memory usage for Tomcat gradually
> increases. Once it reaches 2 GB, Tomcat crashes.

Maximum heap is somewhere around 1.6-1.8 GB on 32 bit Windows, so
I assume that it crashes slightly before 2 GB.

The most probably explanation is that there is a memory leak
in your app.

It is a bit difficult to create a memory leak in Java, but it
is possible.

Arne


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.