In our application when multiple requests are served by JBOSS 6.4 server , we are facing memory leak.
Problem 1
One instance of "org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool" loaded by "org.jboss.modules.ModuleClassLoader @ 0xf10085e8" occupies 17,444,920 (16.96%) bytes. The memory is accumulated in one instance of "char[]" loaded by "<system class loader>".
Keywords
org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool
org.jboss.modules.ModuleClassLoader @ 0xf10085e8
char[]
Problem 2
202 instances of "org.jboss.vfs.spi.JavaZipFileSystem", loaded by "org.jboss.modules.ModuleClassLoader @ 0xf105d828" occupy 25,739,880 (25.02%) bytes.
Biggest instances:
- org.jboss.vfs.spi.JavaZipFileSystem @ 0xf1affef0 - 2,532,632 (2.46%) bytes.
- org.jboss.vfs.spi.JavaZipFileSystem @ 0xf1940828 - 2,162,120 (2.10%) bytes.
- org.jboss.vfs.spi.JavaZipFileSystem @ 0xf20131c0 - 2,069,104 (2.01%) bytes.
These instances are referenced from one instance of "java.util.HashMap$Node[]", loaded by "<system class loader>"
Keywords
org.jboss.vfs.spi.JavaZipFileSystem
java.util.HashMap$Node[]
org.jboss.modules.ModuleClassLoader @ 0xf105d828
