[jboss-jira] [JBoss JIRA] (AS7-3894) remoting3-jmx RemotingConnector mishandles IPv6 addresses

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on AS7-3894:
---------------------------------------

The behavior ^^^ is different from java.net.URL:

     * The format of the host conforms to RFC 2732, i.e. for a
     * literal IPv6 address, this method will return the IPv6 address
     * enclosed in square brackets (<tt>'['</tt> and <tt>']'</tt>).
                
> remoting3-jmx RemotingConnector mishandles IPv6 addresses
> ---------------------------------------------------------
>
>                 Key: AS7-3894
>                 URL: https://issues.jboss.org/browse/AS7-3894
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMX
>    Affects Versions: 7.1.0.Final
>            Reporter: Richard Achmatowicz
>            Assignee: Darran Lofthouse
>            Priority: Critical
>
> 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