VM Crash with WLS 6.1 SP2 JDK 1.3.1 on NT/MSSQL

Question

Has anyone seen this? If we leave the system on for overnight, WLS crashes without
further message. Our setting is 128M, of course it will get out of memory error
if something is asking more than that. Question is:
who is asking for 400 MB in one shot?
P.S. We have internal scheduler threads wake up every 5 minutes to check tasks
thru EJBs.
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested 402653192
bytes
goto finish
cd config\informatica
ENDLOCAL

Answer 1

Thanks, you are right. It's a known bug in JDK 1.3.1 01 and it has been fixed in
JDK 1.3.1 02.
<[email protected]> wrote:
That's the CompileThread asking for 402653192 bytes, so it's probably
has
nothing to do with application, WebLogic or 0x18000008. You can look
at
this bug:
http://developer.java.sun.com/developer/bugParade/bugs/4484290.html
or several other bugs very similar to this one.
Cameron Purdy <[email protected]> wrote:
FWIW - that's hex 0x18000008 ... I'd start by looking through yourcode for
the string "18000" and then grep through the WL code for the ConstantPool
equivalent in the .class files.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Yicheng Tao" <[email protected]> wrote in message
news:3cb48efe$[email protected]..
Has anyone seen this? If we leave the system on for overnight, WLS
crashes
without
further message. Our setting is 128M, of course it will get out of
memory
error
if something is asking more than that. Question is:
who is asking for 400 MB in one shot?
P.S. We have internal scheduler threads wake up every 5 minutes to
check
tasks
thru EJBs.
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested402653192
bytes
goto finish
cd config\informatica
ENDLOCAL
Dimitri