The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
EVALUATION
What is the error? A hang, a crash, an error message?
When I try
$ $Deployed/JDK-1.4.2/bin/java -XX:+UseParNewGC -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
$ $Deployed/JDK-1.4.2/bin/java -XX:+AggressiveHeap -XX:+UseParNewGC -version
Conflicting collector combinations in option list; please refer to the release notes for the combinations allowed
Could not create the Java virtual machine.
on a Solaris/SPARC box (I don't have a Windohs/IA64 box to
test on).
You have to know that -XX:+AggressiveHeap tries to set
-XX:+UseParallelGC, which is then in conflict when the
-XX:+UseParNewGC option is seen. But if you don't know what
-XX:+AggressiveHeap is doing, why are you using it?!
In general, -XX:+AggressiveHeap isn't recommended for programs
that don't look like SPECjbb2000, and is subject to change without
notice. If you like what -XX:+AggressiveHeap does, then I would
suggest finding out what it does (e.g., -XX:+PrintCommandLineFlags
in a JDK-1.5.0 JRE), and explicitly use those options (or the ones
you like and understand).
Meanwhile, your request for a backport will have to be taken up
with CTE.
###@###.### 2004-11-05 22:01:19 GMT
Let me give you more details on the situation: the problem is not only
related to -XX:+AggressiveHeap, it also occurs when using -XX:+UseParNewGC,
-XX:+UseParalleGC, or -XX:+UseConcMarkSweepGC, and there might be others.
The problem is even more confusing considering that on an IA64 bit
machine, I can reproduce it when connecting through Microsoft Remote
Desktop Connection, whereas it works fine when connecting through good
old telnet.
From Bob Vandette, who as I hear created the IA64 port of the JDK, I got
the feedback that he was able to reproduce the problem:
<bob>
I was able to reproduce your problem on my Itanium system. The VM is getting a
data alignment fault in the function os::active_processor_count. This bug
was reported a while ago by Unisys. The bug Id is 4861898.
The bad news is that this bug was fixed in 1.5 but has not been back ported
back to any 1.4.2 release.
</bob>
This is why I created this sub-CR asking for a backport.
Matthias Laux 11-08-04
###@###.### 2004-11-08 07:54:25 GMT