You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2014/03/05 01:01:44 UTC

[jira] [Updated] (SAMZA-50) Log both RMI and JMX ports in internal JMX server

     [ https://issues.apache.org/jira/browse/SAMZA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan updated SAMZA-50:
-----------------------------

    Attachment: SAMZA-50.patch

Forward ported patch we've been using in production.  Explicitly logs both the RMI server and the JMX port.

> Log both RMI and JMX ports in internal JMX server
> -------------------------------------------------
>
>                 Key: SAMZA-50
>                 URL: https://issues.apache.org/jira/browse/SAMZA-50
>             Project: Samza
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 0.6.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.7.0
>
>         Attachments: SAMZA-50.patch
>
>
> Right now we publish log JMX port number so that it can be found dynamically, but in environments where ports are blocked, it's necessary to know both that and the RMI server port in order to do port forwarding. [Here's|http://stackoverflow.com/questions/15093376/jconsole-over-ssh-local-port-forwarding] a more detailed explanation.



--
This message was sent by Atlassian JIRA
(v6.2#6252)