Groups > Weblogic > WebLogic environment > =?UTF-8?Q?[help}_Weblogic8.15_throws_OutOfMemo?=




=?UTF-8?Q?[help}_Weblogic8.15_throws_OutOfMemo?=

=?UTF-8?Q?[help}_Weblogic8.15_throws_OutOfMemo?=
Wed, 1 Aug 2007 02:19:36 -0700
It is thrown while perf testing. Does anybody have similar experience on that?

test env:
1)Hardware: Dell PE1850 2x3.4GB RAM, 2x73GB-raid1
2)OS: Red Hat Enterprise Linux ES release 3
3)weblgoic: weblogic81sp5

log:
<Jul 23, 2007 11:07:12 PM PDT> <Warning> <Socket>
<BEA-000402> <There are: 9 active sockets, but the maximum number of
socket reader threads allowed by the configuration is: 8. You may want to alter
your configuration.> 
<Jul 23, 2007 11:20:34 PM PDT> <Error> <Kernel>
<BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: JVM@jniMalloc (src/jvm/native/jni/jnimodel.c:544).
12 bytes requested. Java heapsize=1073741824, paged memory89209856/208920.
java.lang.OutOfMemoryError: JVM@jniMalloc (src/jvm/native/jni/jnimodel.c:544).
12 bytes requested. Java heapsize=1073741824, paged memory89209856/208920
at java.util.zip.ZipFile.getEntry(Native Method)
at java.util.zip.ZipFile.getEntry(ZipFile.java:150)
at
weblogic.utils.classloaders.ClasspathClassFinder.getSourcesInternal(ClasspathCla
ssFinder.java:337)
at
weblogic.utils.classloaders.ClasspathClassFinder.getSource(ClasspathClassFinder.
java:266)
at weblogic.servlet.internal.WarClassFinder.getSource(WarClassFinder.java:249)
at
weblogic.servlet.internal.WebAppServletContext.getSource(WebAppServletContext.ja
va:4841)
at
weblogic.servlet.internal.WebAppServletContext.findIndexFile(WebAppServletContex
t.java:4732)
at
weblogic.servlet.internal.WebAppServletContext.getIndexServletStub(WebAppServlet
Context.java:4375)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:275
8)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>

Is there any relationship between this exception and JNI? I tried to disable the
weblogic feature "Enable Native IO"
, and I did get better memeory usage (I mean, no OOM), but the CPU usage is
unacceptable (almost 100%), and finally the server stopped serving to all 
Post Reply
about | contact