Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-184

CLONE - Config. XML with <interface ...><any-ipv6-address /></interface> + -Djava.net.preferIPv4Stack=true (default setting) produces mess error message

    Details

      Description

      The same situation is with every shipped and supported configuration/profile. As base for my explanation I'm using standalone.xml. Standalone.xml declares xmlns as:

      <server xmlns="urn:jboss:domain:1.3">
      

      The real XSD file which defined elements is jboss-eap-6.0/docs/schema/jboss-as-config_1_3.xsd.

      The very common Linux system has implemented and enabled dualstack in these days. If we instruct EAP instance to bind to any IPv6 address via

      <interface name="public">
          <any-ipv6-address />
      </interface>

      The real result is mess messages to output log:

      
      08:17:55,779 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Error initializing endpoint: java.net.SocketException: Protocol family unavailable
              at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_30]
              at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_30]
              at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_30]
              at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_30]
              at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:56) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
              at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:978) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
              at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
              at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.15.Final-redhat-0-todo.jar:]
              at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
              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]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
      
      08:17:55,828 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: 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-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]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
      Caused by: LifecycleException:  Protocol handler initialization failed: java.net.SocketException: Protocol family unavailable
              at org.apache.catalina.connector.Connector.init(Connector.java:985)
              at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
              ... 5 more
      
      08:17:55,999 WARN  [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
      08:17:56,294 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.3.GA-redhat-1
      08:17:56,294 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
      08:17:56,904 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/users-tmp/pjanouse/jboss-eap-6.0/standalone/deployments
      08:17:56,918 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999
      08:17:56,953 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
              at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:111)
              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]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
      Caused by: java.net.SocketException: Protocol family unavailable
              at sun.nio.ch.Net.bind(Native Method) [rt.jar:1.6.0_30]
              at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) [rt.jar:1.6.0_30]
              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59) [rt.jar:1.6.0_30]
              at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52) [rt.jar:1.6.0_30]
              at org.xnio.nio.NioXnioWorker.createTcpServer(NioXnioWorker.java:287)
              at org.xnio.XnioWorker.createStreamServer(XnioWorker.java:135)
              at org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:209)
              at org.jboss.as.remoting.AbstractStreamServerService.start(AbstractStreamServerService.java:101)
              ... 5 more
      
      08:17:57,611 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
      JBAS014777:   Services which failed to start:      service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017113: Failed to start service
            service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
      

      The valid result message could be only - there isn't available any IPv6 address when IPv6 is disabled. Or there isn't a such IP address.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                pjanouse Pavel Janousek
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: