[jboss-jira] [JBoss JIRA] (AS7-3752) Socket bind for Http11Apr fails on startup when using link-local IPv6 address
Richard Achmatowicz (JIRA)
jira-events at lists.jboss.org
Wed Feb 15 15:43:36 EST 2012
[ https://issues.jboss.org/browse/AS7-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666886#comment-12666886 ]
Richard Achmatowicz edited comment on AS7-3752 at 2/15/12 3:43 PM:
-------------------------------------------------------------------
For the the record, the problem here is that with link local addresses, you must also set the zoneid (interface id) of the interface on which the link-local address resides. Link-local addresses are only unique to a network segement, so that the same link-local address A:B::C can be defined on two interfaces on the same host. The zone id disabiguates.
Who can this issue be passed onto? Is it logged as an issue with Apache?
was (Author: rachmato):
For the the record, the problem here is that with link local addresses, you must also set the zoneid (interface id) of the interface on which the link-local address resides. Link-local addresses are only unique to a network segement, so that the same link-local address A:B::C can be defined on two interfaces on the same host. The zone id disabiguates.
Who can this issue be passed onto?
> Socket bind for Http11Apr fails on startup when using link-local IPv6 address
> -----------------------------------------------------------------------------
>
> Key: AS7-3752
> URL: https://issues.jboss.org/browse/AS7-3752
> Project: Application Server 7
> Issue Type: Bug
> Components: Web
> Affects Versions: 7.1.0.Final
> Reporter: Richard Achmatowicz
> Assignee: Remy Maucherat
>
> Start AS 7.1.0.Final with a link local IPv6 address:
> {noformat}
> [nrla at lenovo ~]$ /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr F0:DE:F1:40:75:B8
> inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::f2de:f1ff:fe40:75b8/64 Scope:Link
> inet6 addr: 3ffe:ffff:100:f101::1/64 Scope:Global
> [nrla at lenovo ~]$ ./standalone.sh -Djboss.bind.address=fe80::f2de:f1ff:fe40:75b8 -Djboss.bind.address.management=fe80::f2de:f1ff:fe40:75b8
> {noformat}
> and the following exception occurs:
> {noformat}
> 11:01:28,909 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:4447
> 11:01:29,013 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.1.GA
> 11:01:29,185 ERROR [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-6) Error initializing endpoint: java.lang.Exception: Socket bind failed: [22] Invalid argument
> at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:578) [jbossweb-7.0.10.Final.jar:]
> at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) [jbossweb-7.0.10.Final.jar:]
> at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.10.Final.jar:]
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> 11:01:29,254 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [22] Invalid argument
> at org.apache.catalina.connector.Connector.init(Connector.java:985)
> at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
> ... 5 more
> 11:01:29,442 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:9999
> 11:01:29,462 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/nrla/projects/jboss-as/build/target/jboss-as-7.1.0.Final-SNAPSHOT/standalone/deployments
> 11:01:29,615 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 11:01:29,626 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
> 11:01:29,649 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" started (with errors) in 2317ms - Started 133 of 203 services (1 services failed or missing dependencies, 68 services are passive or on-demand)
> {noformat}
> I had a look around and found this related (in fact the same) bug report:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=43327
> Looks like it may have been fixed for IPv6 addresses other than link-local.
> Link-local addresses are used often for running on a local network segment.
--
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