[jboss-jira] [JBoss JIRA] (AS7-4044) Definition of IPv6 address is not possible for <outbound-socket-binding> tag
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Mon Mar 12 04:00:49 EDT 2012
[ https://issues.jboss.org/browse/AS7-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jaikiran pai resolved AS7-4044.
-------------------------------
Fix Version/s: 7.1.1.Final
Resolution: Done
> Definition of IPv6 address is not possible for <outbound-socket-binding> tag
> ----------------------------------------------------------------------------
>
> Key: AS7-4044
> URL: https://issues.jboss.org/browse/AS7-4044
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.0.Final
> Reporter: Ondřej Chaloupka
> Assignee: jaikiran pai
> Labels: eap6_prd_req, remoting
> Fix For: 7.1.1.Final
>
>
> In case that you want want to use IPv6 type of address in outbound-socket-binding tag, like 1:0:0:1::12 or ::1
> {code}
> <outbound-socket-binding name="remote-ejb">
> <remote-destination host="1:0:0:1::12" port="4447"/>
> </outbound-socket-binding>
> {code}
> you get exception:
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.ejb3.dd-based-ejb-client-context."serverclient-ejb.jar": org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context."serverclient-ejb.jar": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23]
> 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:337)
> at org.jboss.as.remoting.RemoteOutboundConnectionService.connect(RemoteOutboundConnectionService.java:130)
> at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.createRemotingConnections(DescriptorBasedEJBClientContextService.java:122)
> at org.jboss.as.ejb3.remote.DescriptorBasedEJBClientContextService.start(DescriptorBasedEJBClientContextService.java:86)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> ... 3 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
More information about the jboss-jira
mailing list