[jboss-jira] [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz edited comment on REMJMX-26 at 3/10/12 1:05 PM:
--------------------------------------------------------------------
Looks like the fix that Stuart provided got whacked in moving to 1.0.2.Final.
See
https://github.com/darranl/remoting-jmx/blob/master/src/main/java/org/jbo...
was (Author: rachmato):
Looks like this change got whacked in moving to 1.0.2.Final.
See
https://github.com/darranl/remoting-jmx/blob/master/src/main/java/org/jbo...
remoting3-jmx RemotingConnector mishandles IPv6 addresses
---------------------------------------------------------
Key: REMJMX-26
URL: https://issues.jboss.org/browse/REMJMX-26
Project: Remoting JMX
Issue Type: Bug
Components: Connection
Affects Versions: 1.0.0.GA
Reporter: Richard Achmatowicz
Assignee: Stuart Douglas
Priority: Blocker
Fix For: 1.0.1.Final
Calls to RemotingConnector do not take account of IPv6 URL conventions when converting
from JMXServiceURLs to URIs:
{noformat}
17:10:35,032 INFO [org.jboss.remoting3.jmx.RemotingConnector] (main) service URL =
service:jmx:remoting-jmx://[0:0:0:0:0:0:0:1]:9999
17:10:35,037 INFO [org.jboss.remoting3.jmx.RemotingConnector] (main) service URI =
remote://0:0:0:0:0:0:0:1:9999
{noformat}
This causes havoc for Arquillian, which uses remoting-jmx to contact servers during
testing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira