[ https://issues.apache.org/jira/browse/ZOOKEEPER-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658703#comment-14658703 ]
Raul Gutierrez Segales commented on ZOOKEEPER-2239: --------------------------------------------------- I'll merge this to trunk and 3.4 (for starters). [~michim]: shall I merge it to the 3.5 branch as well? > JMX State from LocalPeerBean Incorrect > -------------------------------------- > > Key: ZOOKEEPER-2239 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2239 > Project: ZooKeeper > Issue Type: Bug > Components: jmx > Affects Versions: 3.4.6, 3.5.0, 3.5.1 > Environment: All > Reporter: Kevin Lee > Attachments: ZOOKEEPER-2239.patch > > > The "State" property of LocalPeerBean in package > org.apache.zookeeper.server.quorum is returning the incorrect value. It is > performing peer.getState() which is calling the getState() method on > java.lang.Thread instead of getting the server state from > org.apache.zookeeper.server.quorum.QuorumPeer. The Javadoc within > LocalPeerMXBean.java states that it should be returning the server state as > well. The fix is to call peer.getServerState() in the getState() method of > LocalPeerBean instead of peer.getState().toString(). This will return the > states defined in QuorumStats.Provider (unknown, leaderelection, leading, > following, and observing). This issue prevents JMX monitoring of the > Zookeeper server state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)