-
Bug
-
Resolution: Won't Fix
-
P2
-
6
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2212720 | 1.4.0 | Joe Wang | P2 | Closed | Won't Fix |
SHORT SUMMARY:
WEBLOGIC.XML.JAXP.REGISTRYXMLREADER LEAKING THROUGH A THREADLOCAL
at any platform.
INDICATORS:
java.lang.OutOfMemoryError: Java heap space
when
-Xms512m -Xmx512m -XX:NewSize=128m -XX:MaxNewSize=128m -XX:PermSize=128m
-XX:MaxPermSize=128m
or have default values.
COUNTER INDICATORS:
works fine when:
-Xms1024m -Xmx1024m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=128m
-XX:MaxPermSize=128m
TRIGGERS:
See attached test case
KNOWN WORKAROUND:
Increase stackl size (see COUNTER INDICATORS)
PRESENT SINCE:
jre6.
Not tested on jre5 and jre4
HOW TO VERIFY:
Run attached test case
NOTES FOR SE:
None
REGRESSION:
No
}
*** MNIEMIEC 08/02/11 07:34 am *** (CHG: Tag Updated)
*** MNIEMIEC 08/02/11 07:34 am ***
sust:ui
*** SCOFFEY 08/02/11 08:49 am *** (CHG: Comp. Ver-> 6.0 -> 1.6.0)
*** SCOFFEY 08/02/11 08:49 am *** (CHG: Asg->JDKREP)
*** SCOFFEY 08/02/11 08:50 am *** (CHG: Asg->MNIEMIEC)
How to reproduce the bug:
-------------------------
- Compile StopWatch.java and XmlTest.java in your test directory.
- Copy dummy.xml and dummy.xsl to your test directory.
- Create empty heaps, logs, tmp directories in your test directory.
- Run XmlTest as follows:
java -XX:HeapDumpPath=./heaps/$$_dump.hprof -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:logs/$$_gc.log -XX:ParallelGCThreads=4 -XX:+HeapDumpOnOutOfMemoryError XmlTest
You'll get following output:
java.lang.OutOfMemoryError: Java heap space
Dumping heap to ./heaps/$$_dump.hprof ...
Exception in thread "pool-1-thread-5" java.lang.OutOfMemoryError: Java heap space
WEBLOGIC.XML.JAXP.REGISTRYXMLREADER LEAKING THROUGH A THREADLOCAL
at any platform.
INDICATORS:
java.lang.OutOfMemoryError: Java heap space
when
-Xms512m -Xmx512m -XX:NewSize=128m -XX:MaxNewSize=128m -XX:PermSize=128m
-XX:MaxPermSize=128m
or have default values.
COUNTER INDICATORS:
works fine when:
-Xms1024m -Xmx1024m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=128m
-XX:MaxPermSize=128m
TRIGGERS:
See attached test case
KNOWN WORKAROUND:
Increase stackl size (see COUNTER INDICATORS)
PRESENT SINCE:
jre6.
Not tested on jre5 and jre4
HOW TO VERIFY:
Run attached test case
NOTES FOR SE:
None
REGRESSION:
No
}
*** MNIEMIEC 08/02/11 07:34 am *** (CHG: Tag Updated)
*** MNIEMIEC 08/02/11 07:34 am ***
sust:ui
*** SCOFFEY 08/02/11 08:49 am *** (CHG: Comp. Ver-> 6.0 -> 1.6.0)
*** SCOFFEY 08/02/11 08:49 am *** (CHG: Asg->JDKREP)
*** SCOFFEY 08/02/11 08:50 am *** (CHG: Asg->MNIEMIEC)
How to reproduce the bug:
-------------------------
- Compile StopWatch.java and XmlTest.java in your test directory.
- Copy dummy.xml and dummy.xsl to your test directory.
- Create empty heaps, logs, tmp directories in your test directory.
- Run XmlTest as follows:
java -XX:HeapDumpPath=./heaps/$$_dump.hprof -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:logs/$$_gc.log -XX:ParallelGCThreads=4 -XX:+HeapDumpOnOutOfMemoryError XmlTest
You'll get following output:
java.lang.OutOfMemoryError: Java heap space
Dumping heap to ./heaps/$$_dump.hprof ...
Exception in thread "pool-1-thread-5" java.lang.OutOfMemoryError: Java heap space
- backported by
-
JDK-2212720 weblogic.xml.jaxp.registryxmlreader leaking through a threadlocal.
-
- Closed
-