[jboss-jira] [JBoss JIRA] Commented: (JBAS-8455) HTTP InvokerLocators being formed incorrectly with IPv6 bind address
[
https://jira.jboss.org/browse/JBAS-8455?page=com.atlassian.jira.plugin.sy...
]
Richard Achmatowicz commented on JBAS-8455:
-------------------------------------------
A fix has been created for this issue and applied to the AS 6 IPv6 branch. All that
remains is to patch AS 6 trunk with the patch.
With the fix, I am applying the method described above where full URLs are passed in as
attrubutes and SBM is used to construct the strings.
There are addition changes required to fix the Http and HttpHA invokers when URL [prefixes
and suffixes are passed in. These were picked up
from the EAP 4.3 IPv6 changes and won't be described here.
HTTP InvokerLocators being formed incorrectly with IPv6 bind address
--------------------------------------------------------------------
Key: JBAS-8455
URL: https://jira.jboss.org/browse/JBAS-8455
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Integration
Affects Versions: 6.0.0.M4
Reporter: Richard Achmatowicz
Assignee: Shelly McGowan
Fix For: TBD-6.x
When we boot the AS using an IPv6 bind address, many HTTP invoker locators are formed
incorrectly as URLs.
For example, for the MBean service=invoker,type=httpHA, its invoker locator is given as:
http://3ffe:ffff:0100:f101::1:8080/invoker/EJBInvokerHAServlet
instead of the correct:
http://[3ffe:ffff:0100:f101::1]:8080/invoker/EJBInvokerHAServlet
The source of the problem is in the Http Invoker Service Configuration, defined in
deploy/httpha.invoker.sar/META-INF/jboss-service.xml, where the invoker locators are
constructed. The URLs are constructed by taking the hostname and port, appending a fixed
prefix and appending a fixed suffix, without taking the type of IP address into account.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira