4:32 p.m.
Richard Achmatowicz created AS7-3894:
----------------------------------------
Summary: 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: Remoting
Affects Versions: 7.1.0.Final
Reporter: Richard Achmatowicz
Assignee: David Lloyd
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
4:34 p.m.
[
https://issues.jboss.org/browse/AS7-3894?page=com.atlassian.jira.plugin.s...
]
David Lloyd updated AS7-3894:
-----------------------------
Assignee: Darran Lofthouse (was: David Lloyd)
Component/s: JMX
(was: Remoting)
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
4:34 p.m.
[
https://issues.jboss.org/browse/AS7-3894?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3894:
------------------------------------------
Possible fix:
{noformat}
private URI convert(final JMXServiceURL serviceUrl) throws IOException {
String host = serviceUrl.getHost();
int port = serviceUrl.getPort();
// check for IPv6 address literal
if ((InetAddress.getByName(host) instanceof Inet6Address) &&
(host.indexOf(":") > -1)) {
host = "[" + host + "]" ;
}
try {
return new URI(CONNECTION_PROVIDER_URI + "://" + host + ":" +
port);
} catch (URISyntaxException e) {
throw new IOException("Unable to create connection URI", e);
}
}
{noformat}
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
4:36 p.m.
[
https://issues.jboss.org/browse/AS7-3894?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz commented on AS7-3894:
------------------------------------------
Also noted that the pom references remoting 3.2.0.GA whereas AS7 uses 3.2.2.GA.
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
6:28 p.m.
[
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
6:32 p.m.
[
https://issues.jboss.org/browse/AS7-3894?page=com.atlassian.jira.plugin.s...
]
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
4:50 a.m.
[
https://issues.jboss.org/browse/AS7-3894?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-3894:
----------------------------------
Priority: Major (was: Critical)
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
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
4:52 a.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Darran Lofthouse moved AS7-3894 to REMJMX-26:
---------------------------------------------
Project: Remoting JMX (was: Application Server 7)
Key: REMJMX-26 (was: AS7-3894)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: 1.0.0.GA
(was: 7.1.0.Final)
Component/s: Connection
(was: JMX)
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: Darran Lofthouse
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
4:54 a.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Darran Lofthouse updated REMJMX-26:
-----------------------------------
Fix Version/s: 1.0.1.Final
Priority: Blocker (was: Major)
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: Darran Lofthouse
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
5:53 a.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on REMJMX-26:
----------------------------------------
BTW the Remoting version does not need noting - there is no guarantee that components will
always have their versions exactly in sync.
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: Darran Lofthouse
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
5:33 a.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Darran Lofthouse updated REMJMX-26:
-----------------------------------
Assignee: Stuart Douglas (was: Darran Lofthouse)
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
5:33 a.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Darran Lofthouse resolved REMJMX-26.
------------------------------------
Resolution: Done
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
12:04 p.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz reopened REMJMX-26:
---------------------------------------
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
12:06 p.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz commented on REMJMX-26:
-------------------------------------------
I'm seeing the same behaviours in the testsuite when running with IPv6 addreses.
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
12:06 p.m.
New subject: [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
12:20 p.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz resolved REMJMX-26.
---------------------------------------
Resolution: Done
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
12:20 p.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz resolved REMJMX-26.
---------------------------------------
Resolution: Rejected
Looks like a false alarm. Problem seems to be elsewhere.
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
12:20 p.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz reopened REMJMX-26:
---------------------------------------
Reopening to change resolution to correct one.
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
4:56 a.m.
New subject: [JBoss JIRA] (REMJMX-26) remoting3-jmx RemotingConnector mishandles IPv6 addresses
[
https://issues.jboss.org/browse/REMJMX-26?page=com.atlassian.jira.plugin....
]
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
4671
days inactive
4689
days old
18 comments
4 participants
participants (4)
-
Brian Stansberry (JIRA) -
Darran Lofthouse (JIRA)
-
David Lloyd (JIRA)
-
Richard Achmatowicz (JIRA)