[jboss-jira] [JBoss JIRA] (AS7-3894) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/AS7-3894?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-3894:
---------------------------------------
The problem is caused by this bit of behavior noted in the JMXServiceURL.getHost()
javadoc:
*
* <p>In either case, if the host was specified using the
* <code>[...]</code> syntax for numeric IPv6 addresses, the
* square brackets are not included in the return value here.</p>
*
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