You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Benjamin Reed (JIRA)" <ji...@apache.org> on 2009/02/02 12:55:59 UTC

[jira] Created: (ZOOKEEPER-284) JMX doesn't get the clientPort correctly

JMX doesn't get the clientPort correctly
----------------------------------------

                 Key: ZOOKEEPER-284
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-284
             Project: Zookeeper
          Issue Type: Bug
    Affects Versions: 3.1.0
            Reporter: Benjamin Reed
            Assignee: Patrick Hunt
            Priority: Minor
             Fix For: 3.1.0


The client port in JMX is always zero. it should be getting the client port from the cnxnfactory. it's a pretty easy fix. the really problem is that we have a setter for the clientPort as well, which is a bit more complicated to implement correctly. do we need a setter for the clientPort? i think we should make it a readonly attribute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (ZOOKEEPER-284) JMX doesn't get the clientPort correctly

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar resolved ZOOKEEPER-284.
-------------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

ZOOKEEPER-286 has been committed. So closing this one.

> JMX doesn't get the clientPort correctly
> ----------------------------------------
>
>                 Key: ZOOKEEPER-284
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-284
>             Project: Zookeeper
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>            Reporter: Benjamin Reed
>            Assignee: Patrick Hunt
>            Priority: Minor
>             Fix For: 3.1.0
>
>
> The client port in JMX is always zero. it should be getting the client port from the cnxnfactory. it's a pretty easy fix. the really problem is that we have a setter for the clientPort as well, which is a bit more complicated to implement correctly. do we need a setter for the clientPort? i think we should make it a readonly attribute.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.