java/140002: java/diablo-jdk16: jconsole dumps tomcat when contacting jmxrmi service
dteske at FreeBSD.org
dteske at FreeBSD.org
Tue Dec 18 05:33:34 UTC 2012
Synopsis: java/diablo-jdk16: jconsole dumps tomcat when contacting jmxrmi service
State-Changed-From-To: closed->open
State-Changed-By: dteske
State-Changed-When: Tue Dec 18 05:14:22 UTC 2012
State-Changed-Why:
Re-opening. Since it's been a while since this PR was closed (greater than
3 years), I'm attaching some details:
FreeBSD dcs5.dev.vicor.com 8.1-RELEASE-p6 FreeBSD 8.1-RELEASE-p6 #6: Mon Oct 17 11:57:29 PDT 2011 dteske at oos0a.vbsd.vicor.com:/usr/src/sys/amd64/compile/FIS-amd64 amd64
openjdk version "1.6.0"
OpenJDK Runtime Environment (build 1.6.0-b19)
OpenJDK 64-Bit Server VM (build 16.0-b13, mixed mode)
NOTE: This is from binary package available via ftp-archive for 8.1-R amd64
NOTE: We also tested (and reproduced the same problem) with the following...
openjdk version "1.7.0"
OpenJDK Runtime Environment (build 1.7.0-root_2010_06_29_13_39-b00)
OpenJDK 64-Bit Server VM (build 17.0-b10, mixed mode)
And, finally...
tomcat version 7.0.20 compiled from ports with zero modifications.
When we use the following JVM we don't see the problem:
java version "1.6.0_07"
Diablo Java(TM) SE Runtime Environment (build 1.6.0_07-b02)
Diablo Java HotSpot(TM) 64-Bit Server VM (build 10.0-b23, mixed mode)
NOTE: The non-working JVMs (that cause tomcat to dump when connecting with jconsole) are binary packages downloaded via ftp-archive while the diablo-jdk is (as-required) built from ports (also with zero modifications).
Additional testing/details to come.
http://www.freebsd.org/cgi/query-pr.cgi?pr=140002
More information about the freebsd-java
mailing list