You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by pal899 <pa...@futurespace.es> on 2009/06/09 18:54:30 UTC

Memory Leak using EJBs

We are having a memory leak in tomcat 6.0.18. We are using it as a client of
a Weblogic Server 10. We have monitored the memory consumed and we have
noticed that it grows up permanently. We have extended the memory VM
parameters till 1G and it's only a way to delay the end: the free memory is
empty, the GC is not able to free no more byte and the CPU is 100% consumed
by the GC work. At the end Tomcat Server doesn't accept more http petitions
and must be restarted.

Besides, We have studied the VM memory using jmap and importing it using
Eclipse Memory Analizer. We have seen some strange memory blocks of several
Mbytes that are always growing up and that are stored under data structures
in the package com.sun.corba:

     com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl    
(4.5Mb)
        |
         -> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl         
            |
             -> java.util.Hashtable
                 |
                  -> java.util.Hashtable$Entry
                     | 
                      -> java.util.Hashtable$Entry
                      -> java.util.Hashtable$Entry
                      .....
                      -> java.util.Hashtable$Entry


Has anybody has a problem like that?

Thanks in advance.


-- 
View this message in context: http://www.nabble.com/Memory-Leak-using-EJBs-tp23947002p23947002.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


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