[jboss-jira] [JBoss JIRA] Commented: (JBAS-4872) Invalid URI if the jboss.bind.address is IPv6

[Ron Sigal (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422334#action_12422334 ] 

Ron Sigal commented on JBAS-4872:
---------------------------------

Takayoshi,

With the resolution of 

  * JBREM-852 "Verify IPv6 addresses are handled correctly" in Remoting 2.2.2.SP4 and 
  * JBREM-1003 "Verify IPv6 addresses are handled correctly, part 2" in 2.2.2.SP8, 

I think this issue can be closed.  Do you want to verify any test cases, or should I just close it?

-Ron

> Invalid URI if the jboss.bind.address is IPv6
> ---------------------------------------------
>
>                 Key: JBAS-4872
>                 URL: https://jira.jboss.org/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
>            Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira