When launching jconsole on my local machine and connecting to the remote jmx service, tomcat dumps core. Java is: java version "1.6.0_03-p4" Java(TM) SE Runtime Environment (build 1.6.0_03-p4-root_18_nov_2008_12_28-b00) Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-p4-root_18_nov_2008_12_28-b00, mixed mode) Fix: Not known. Patch attached with submission follows: How-To-Repeat: Add the following to catalina.sh under CATALINA_OPTS -Dcom.sun.management.jmxremote.port=7090 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false and restart tomcat. start jconsole and use the service address of: service:jmx:rmi:///jndi/rmi://192.168.100.100:7090/jmxrmi
I forgot to mention the version of tomcat that I am using. It is: tomcat-5.5.23 Thanks! Jason
This issue can be closed. When running openjdk-b17 on server and client, there are no issues, and jconsole runs as intended. -jgh
State Changed From-To: open->closed Apparently fixed in the latest revisions of the ports.
This should be re-opened, as I've learned recently that jconsole jmx service should work if the jvm was built with or without debugging. These errors were thrown in this case of "without." I was able to get jconsole jmx service to work only if built with debugging symbols. I have been working with Brian on this, however I figured, I may as well reopen this PR. Thanks, Jason
State Changed From-To: closed->open 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@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.
State Changed From-To: open->feedback I cannot reproduce the problem. Can you please try the latest ports?
How this bug can be in 2 statuses in same time? Top of the page: "Status: In Progress". Comment from Jung-uk Kim freebsd_committer 2014-05-22 00:16:34 UTC: "Status: Open → Closed"