[jboss-jira] [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses

Mon Mar 12 05:56:47 EDT 2012

    [ https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675866#comment-12675866 ] 

Darran Lofthouse commented on REMJMX-26:
----------------------------------------

Do not re-open issues marked as resolved against a released version - if an issue occurs again it is a new issue and a new Jira needs to be created, feel free to link to the original problem for context but do not break the release notes history in Jira by moving already resolved issues to different releases.

> 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