| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2121269 | 1.4.2_08 | Poonam Bajaj Parhar | P2 | Resolved | Fixed | b02 |
We've recently noticed a problem with -XX:+AggressiveHeap. When we run SPECjbb,
even with a simple command line:
java -XX:+AggressiveHeap -Xmn2000m -Xms6000m -Xmx6000m -cp ... spec
classpath etc. ...
the JVM processes for ~10 seconds and then returns to the Windows Command Prompt
-- no errors reported.
** This problem started with build 22 **
Any suggestions for tracing options to determine where this problem might be?
even with a simple command line:
java -XX:+AggressiveHeap -Xmn2000m -Xms6000m -Xmx6000m -cp ... spec
classpath etc. ...
the JVM processes for ~10 seconds and then returns to the Windows Command Prompt
-- no errors reported.
** This problem started with build 22 **
Any suggestions for tracing options to determine where this problem might be?
- backported by
-
JDK-2121269 -XX:+AggressiveHeap broken in build 1.4.2_22 for Windows/IA64
-
- Resolved
-
- relates to
-
JDK-4831461 JNI GetEnv() race with ThreadLocalStorage::set_thread() guarantee
-
- Closed
-