[ https://issues.apache.org/jira/browse/DAEMON-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831910#comment-16831910 ]
Michael Osipov commented on DAEMON-388: --------------------------------------- The whole point is that the behavior is different to the one in java directly. I'd expect this to be as similar as possible or properly documented. > jsvc does not play nice with JMX > -------------------------------- > > Key: DAEMON-388 > URL: https://issues.apache.org/jira/browse/DAEMON-388 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc > Affects Versions: 1.1.0 > Environment: FreeBSD 10.4-STABLE #22 r333394: Wed May 9 08:53:46 > CEST 2018 i386 > Reporter: Michael Osipov > Priority: Major > > * Installed Commons Daemon through Ports, installed Tomcat 8.5 (uses JSVC) > through Ports. > * Started Tomcat > * Launched JConsole locally to attach to VM > The VM does not display with its PID. After some search, I figured out that > {{com.sun.management.jmxremote}} is not set, but enabled by {{java(1)}} since > version 6. I'd expect the same behavior. After setting it, the VM is visible > in JConsole, but the startup class is not visible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)