[
https://jira.jboss.org/jira/browse/JBREM-1164?page=com.atlassian.jira.plu...
]
Richard Achmatowicz commented on JBREM-1164:
--------------------------------------------
Apolgies for the delay in responding to your posting, Ron. Got bogged down a bit.
I am in complete agreement with your analysis. In the interim, I was working on
JBPAPP-3018, and found that all Remoting IPv6 issues could be solved with two mechanisms:
(i) a change to Connector to cause it to check for and properly construct InvokerLocator
URIs, assuming that the serverBindAddress does not contain enclosing brackets (as you
rightly pointed out that it should not)
(ii) when specifying InvokerLocator URLs explicitly, use a newly defined system property
jboss.bind.url.address in place of jboss.bind.address in the URL
(e.g socket://${jboss.bind.url.address}:${port}) where the function of this system
property is to provide a hostname suitable for enclosure in a URL. This was suggested by
DML.
Only the former requires a change, and I gave an example patch on JBPAPP-3018. With these
two changes in place, the AS 4.2.x CP branch seems to start OK. Checking JNDIView and the
logs reveals no remoting related IPv4 addresses when binding with an IPv6 bind address.
This isn't a guarantee that all is well, but its a good start. Unfortunately, there
are other issues to work out before we can run the testsuite with IPv6 bind addresses and
no brackets.
The change also does not affect existing IPv4 usage.
Remoting shouldn't require IPv6 addresses to be surrounded by
brackets
----------------------------------------------------------------------
Key: JBREM-1164
URL:
https://jira.jboss.org/jira/browse/JBREM-1164
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.5.2 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2.SP1 (Flounder)
Although IPv6 addresses are surrounded by brackets in URLs, the addresses themselves
don't have brackets. Thus, it should be possible to start the Application Server
with
run.sh -b ::1
instead of requiring
run.sh -b [::1]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira