4:23 a.m.
jaikiran pai created AS7-4762:
---------------------------------
Summary: Remote naming fails to work with IPv6 provider URL
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: John Bailey
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:23 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4762:
-----------------------------------
Assigning to myself.
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: John Bailey
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:23 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
jaikiran pai reassigned AS7-4762:
---------------------------------
Assignee: jaikiran pai (was: John Bailey)
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:47 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek commented on AS7-4762:
-------------------------------------
Jaikiran,
don't forget also for +zone id+ identifier as optional part of *any* IPv6 address like
::1%lo or ::1%1.
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4762:
-----------------------------------
A pull request has been sent to upstream remote-naming project
https://github.com/jbossas/jboss-remote-naming/pull/7
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:02 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4762:
-----------------------------------
Pavel, the zone id handling on the side initiating the connection, is a known JDK issue
which cannot be fixed consistently on all platforms. See Jason's comment here
https://issues.jboss.org/browse/JBPAPP-8833 and also the Release Notes Text field in that
JIRA.
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:06 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4762:
-------------------------------------
remote://::1:4447 is not correct URL syntax. In this case we expect the user to simply
provide a correct IPv6 URL, namely remote://[::1]:4447.
If we are passed an incorrect URL we should not try and guess at what the correct URL
should be IMHO
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:12 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek commented on AS7-4762:
-------------------------------------
+1 with Stuart, we should arrange some "standard" way and use it in any place
without inconsistency (as -b with [] and -bmanagement without [] for ex.).
I preffer:
- Literal IPv6 address is without [] at all and anywhere ([] isn't the part of any
IPv6 address at all as not defined in any RFC)
- URL with literal IPv6 address is with [] always (as defined in informational RFC)
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:12 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek commented on AS7-4762:
-------------------------------------
Jaikiran,
thank you, I didn't aware (nor caught) of mentioned issue, well take my comment only
as note about needed support in the future.
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:22 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4762:
-----------------------------------
{quote}
remote://::1:4447 is not correct URL syntax. In this case we expect the user to simply
provide a correct IPv6 URL, namely remote://[::1]:4447.
{quote}
I actually used an incorrect example in this JIRA, trying to explain the issue. This issue
affects other IPv6 addresses like fe80::250:56ff:fec0:1. Using ::1 wasn't really an
intention.
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Fix For: No Release
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:29 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4762:
-------------------------------------
remote://fe80::250:56ff:fec0:1:447 is not a valid URL either
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Fix For: No Release
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:36 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek commented on AS7-4762:
-------------------------------------
Moreover this example{code}remote://fe80::250:56ff:fec0:1:447{code}is ambiguous as well.
You can read remote://fe80::250:56ff:fec0:1:447 as:
- connect to IPv6 address fe80::250:56ff:fec0:1:447 address to default port (*)
- connect to IPv6 address fe80::250:56ff:fec0:1 port 447
(*) I'm not sure if remoting protocol scheme has defined well-known default port
similarly as http or https, but idea is the same...
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Fix For: No Release
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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:38 a.m.
[
https://issues.jboss.org/browse/AS7-4762?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-4762:
-----------------------------------
I believe Stuart is right. I wasn't paying attention that the user here is passing in
the complete URI and not the individual parts. So I believe it's the responsibility of
the user to pass in the correct IPv6 formatted URI.
For reference, here's our IRC discussion on this:
{quote}
(05:02:05 IST) Jaikiran: stuartdouglas: maybe i'm missing something, but why
isn't that latest one not a valid ipv6 address?
(05:02:47 IST) stuartdouglas: The URL spec says that you need to add [] around the ip
address in IPv6 URL's
(05:03:01 IST) stuartdouglas: so in this case it is the clients responsibility to pass in
a valid URL
(05:03:24 IST) stuartdouglas: in the cases where we are building a URL from an IP address
we need to add the brackets
(05:03:27 IST) Jaikiran: but we don't enforce that on server side for example the -b
part
(05:03:44 IST) stuartdouglas: but if they are passing us a complete URL then it needs to
have the []
(05:03:51 IST) stuartdouglas: That is because they just pass in an IP address
(05:03:52 IST) Jaikiran: ah ok, i see what you mean
(05:03:53 IST) stuartdouglas: not a URL
(05:04:03 IST) Jaikiran: yeah, good point actually
(05:04:07 IST) Jaikiran: i hadn't considered that
(05:04:43 IST) Jaikiran: so false alarm, i'll update that jira with these comments
{quote}
I'll mark this as not a bug.
Remote naming fails to work with IPv6 provider URL
--------------------------------------------------
Key: AS7-4762
URL: https://issues.jboss.org/browse/AS7-4762
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.2.Final (EAP)
Reporter: jaikiran pai
Assignee: jaikiran pai
Priority: Critical
Fix For: No Release
Remote naming doesn't handle IPv6 addresses (like ::1) correctly which leads to
connection creation failures for code like:
{code}
final Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jboss.naming.remote.client.InitialContextFactory");
env.put(Context.PROVIDER_URL, "remote://::1:4447);
context = new InitialContext(env);
// Perform the JNDI lookups
context.lookup("java:jboss/exported/jms/queue/test);
{code}
This fails with:
{code}
Caused by: java.lang.IllegalArgumentException: destination address may not be null
at
org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:98)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
at
org.jboss.naming.remote.client.EndpointCache$EndpointWrapper.connect(EndpointCache.java:105)
at
org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:55)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)
at
org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)
at
org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)
... 10 more
{code}
--
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
5182
days inactive
5182
days old
12 comments
3 participants
participants (3)
-
jaikiran pai (JIRA) -
Pavel Janousek (JIRA)
-
Stuart Douglas (JIRA)