[
https://issues.apache.org/jira/browse/WHIRR-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091696#comment-13091696
]
Karel Vervaeke commented on WHIRR-358:
--------------------------------------
Are you sure? According to the second reply in that post, it binds to 0.0.0.0.
IIRC I *did* have a problem connecting from a remote machine, and I ended using
ssh -L 10101:localhost:10101 without further consideration to the issue.
Honestly, I think solving WHIRR-368 or (as Tom pointed out) WHIRR-370 would be
better than solving this bug. (But that doesn't solve the problem with
configuring JMX for remote connections)
> Enable remote JMX access for HBase
> ----------------------------------
>
> Key: WHIRR-358
> URL: https://issues.apache.org/jira/browse/WHIRR-358
> Project: Whirr
> Issue Type: Improvement
> Components: service/hbase
> Reporter: Karel Vervaeke
> Attachments: WHIRR-358.patch
>
>
> Enabling remote jmx access should make certain management tasks easier.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
