Ramki,
Can you do the following to be sure that hotspot did not take the parameter?
java -XX:ConcGCThreads=1 -XX:+PrintFlagsFinal
I am using jdk9b154, the output shows it changed the ConcGCThreads to 1
Thanks
Jenny
On 4/17/2017 4:33 PM, Ram Krishnan wrote:
Many thanks Jonathan for the immediate reply.
I am copying the hotspot gc team.
Hotspot gc team -- your help would be much appreciated on the topic below.
Thanks,
Ramki
On Mon, Apr 17, 2017 at 2:29 PM, Jonathan Gibbons
<jonathan.gibb...@oracle.com <mailto:jonathan.gibb...@oracle.com>> wrote:
On 04/17/2017 02:18 PM, Ram Krishnan wrote:
Hi,
I have been able to successfully run all the tests in
hotspot/test/gc/g1 using jtreg.
The only gotcha I am facing is that the JVM startup options
specified in process builder does not have any effect. I have
confirmed this through prints in the JVM code base.
For example,
/hotspot/test/gc/g1/
TestEagerReclaimHumongousRegionsClearMarkBits.java modifies the
"-XX:ConcGCThreads=1", but inside the JVM code to value of
ConcGCThreads is still zero.
I am new to jtreg and openjdk and probably missing something
obvious. Your help would be much appreciated.
Thanks in advance,
Ramki
Ramki,
This does not look like an issue with jtreg, since the behavior
you are apparently seeing is all within the test code and its
libraries.
You might want to follow up with the Hotspot team, who would have
more familiarity with these tests and the associated libraries.
-- Jon
--
Thanks,
Ramki
_______________________________________________
hotspot-gc-use mailing list
hotspot-gc-use@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
