[ https://issues.apache.org/jira/browse/ZOOKEEPER-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664125#action_12664125 ]
Flavio Paiva Junqueira commented on ZOOKEEPER-234: -------------------------------------------------- +1. I have followed the steps Patrick describes, omitting of course the commit step. I have actually been able to connect using jconsole remotely, but in this case I had to use more parameters. Here is the command I used: java -cp .:./zookeeper-dev.jar:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar -Dlog4j.configuration=log4j_console.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12122 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg I'll open a jira to document these options upon Pat's request. > Eliminate using statics to initialize the sever. Should allow server to be > more embeddable in OSGi enviorments. > ---------------------------------------------------------------------------------------------------------------- > > Key: ZOOKEEPER-234 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234 > Project: Zookeeper > Issue Type: Improvement > Components: server > Reporter: Hiram Chirino > Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-234_step1.patch, ZOOKEEPER-234_step3.patch > > > Patrick request I open up this in issue in this [email > thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html] > The main culprit I've noticed is: > {code} > ServerStats.registerAsConcrete(); > {code} > But there may be others. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.