[
http://jira.jboss.com/jira/browse/JBAS-4872?page=comments#action_12383170 ]
Takayoshi Kimura commented on JBAS-4872:
----------------------------------------
Another workaround:
Use-b [::1] instead of -b ::1. Somehow it works.
$ ./run.sh -b \[::1\]
Invalid URI if the jboss.bind.address is IPv6
---------------------------------------------
Key: JBAS-4872
URL:
http://jira.jboss.com/jira/browse/JBAS-4872
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Remoting
Affects Versions: JBossAS-4.2.1.GA
Reporter: Takayoshi Kimura
Assigned To: Ron Sigal
JBossRemoting uses jboss.bind.address in URI like the following:
socket://${jboss.bind.address}:4446/?datatype=invocation
However, if the jboss.bind.address is IPv6, it should be inside
of square brackets.
Invalid URI
socket://::1:4446/?datatype=invocation
Valid URI
socket://[::1]:4446/?datatype=invocation
To reproduce this issue:
Run JBoss instance by the following commend on IPv6 enabled system.
$ ./run.sh -c default -b ::1
Workaround:
Edit JBossRemoting URL not to use jboss.bind.address.
Note:
IPv6 address cannot be parsed with JBossRemoting 2.2.1.GA bundled in 4.2.1.GA. IPv6
parsing needs updated version of JBossRemoting.
http://jira.jboss.com/jira/browse/JBREM-645
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira