9 Replies Latest reply on Jan 17, 2014 5:39 AM by erasmo2 marciano2

    Cannot bind the domain controller to 0.0.0.0

    Alexis Hassler Apprentice

      When I launch my domain controller with argument -Djboss.bind.address.management=0.0.0.0, the servers are starting with the foolowing message :

       

      ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://0.0.0.0:9999. The connection timed out
      

       

      I have to start my domain controller on a specific address :

       

      bin/domain.sh -Djboss.bind.address.management=192.168.1.6
      

       

      Is there an other way to bind my domain controller to several addresses ?

       

      (I'm trying JBoss AS 7.1.0.CR1b)

       

      Alexis

        • 1. Re: Cannot bind the domain controller to 0.0.0.0
          Emanuel Muckenhuber Master

          Currently I don't think there is another way to do this. However we have a jira issue in case you want to track this: https://issues.jboss.org/browse/AS7-2758

          1 of 1 people found this helpful
          • 2. Re: Cannot bind the domain controller to 0.0.0.0
            Alexis Hassler Apprentice

            Thanks for the input, I'll track the issue.

            • 3. Re: Cannot bind the domain controller to 0.0.0.0
              Jose Chavez Newbie

              The issue you reference, AS7-2758, indicate the solution was provided in JBOSS AS 7.1.0. However, I am running 7.1.1 final and running into the same problem. In my case I've tried not only overriding the interface from command line using: domain.sh -b=0.0.0.0 -bmanagement=0.0.0.0 but I have also tried modifying the domain controller/master host.xml and specifying the tag:

               

              <interface name="management">
                          <any-address/>
              </interface>

               

              which results in the same errors being produced on startup, pasted below:

               

              [Server:server-one] 14:46:07,730 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.teiid.tuple_buffer: org.jboss.msc.service.StartException in service jboss.teiid.tuple_buffer: java.lang.IllegalArgumentException: failed to start server socket
              [Server:server-one]     at org.teiid.jboss.TupleBufferCacheService.start(TupleBufferCacheService.java:46)
              [Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
              [Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
              [Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_25]
              [Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_25]
              [Server:server-one]     at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_25]
              [Server:server-one] Caused by: java.lang.IllegalArgumentException: failed to start server socket
              [Server:server-one]     at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:302)
              [Server:server-one]     at org.jgroups.protocols.FD.down(FD.java:308)
              [Server:server-one]     at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:77)
              [Server:server-one]     at org.jgroups.protocols.BARRIER.down(BARRIER.java:94)
              [Server:server-one]     at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:526)
              [Server:server-one]     at org.jgroups.protocols.UNICAST2.down(UNICAST2.java:485)
              [Server:server-one]     at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:328)
              [Server:server-one]     at org.jgroups.protocols.pbcast.GMS.down(GMS.java:916)
              [Server:server-one]     at org.jgroups.protocols.FlowControl.down(FlowControl.java:351)
              [Server:server-one]     at org.jgroups.protocols.FlowControl.down(FlowControl.java:351)
              [Server:server-one]     at org.jgroups.protocols.FRAG2.down(FRAG2.java:147)
              [Server:server-one]     at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1033)
              [Server:server-one]     at org.jgroups.JChannel.down(JChannel.java:730)
              [Server:server-one]     at org.jgroups.JChannel.connect(JChannel.java:290)
              [Server:server-one]     at org.jgroups.JChannel.connect(JChannel.java:261)
              [Server:server-one]     at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563)
              [Server:server-one]     at org.teiid.jboss.TupleBufferCacheService.start(TupleBufferCacheService.java:44)
              [Server:server-one]     ... 5 more
              [Server:server-one] Caused by: java.net.BindException: bind_addr /0.0.0.0 is not a valid interface: java.net.BindException: Address already in use
              [Server:server-one]     at org.jgroups.util.Util.createServerSocket(Util.java:3181)
              [Server:server-one]     at org.jgroups.protocols.FD_SOCK.startServerSocket(FD_SOCK.java:562)
              [Server:server-one]     at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:299)
              [Server:server-one]     ... 21 more
              [Server:server-one] 14:46:07,741 ERROR [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID40088 Could not replicate object org.teiid.jboss.EventDistributorFactoryService@c137bc9: java.lang.IllegalArgumentException: failed to start server socket
              [Server:server-one]     at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:302) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.FD.down(FD.java:308) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:77) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.BARRIER.down(BARRIER.java:94) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:526) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.UNICAST2.down(UNICAST2.java:485) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.pbcast.STABLE.down(STABLE.java:328) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.pbcast.GMS.down(GMS.java:916) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.FlowControl.down(FlowControl.java:351) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.FRAG2.down(FRAG2.java:147) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1033) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.JChannel.down(JChannel.java:730) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.JChannel.connect(JChannel.java:290) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.JChannel.connect(JChannel.java:261) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.teiid.replication.jgroups.JGroupsObjectReplicator.replicate(JGroupsObjectReplicator.java:563) [teiid-runtime-8.2.0.Final.jar:8.2.0.Final]
              [Server:server-one]     at org.teiid.services.AbstractEventDistributorFactoryService.start(AbstractEventDistributorFactoryService.java:60) [teiid-runtime-8.2.0.Final.jar:8.2.0.Final]
              [Server:server-one]     at org.teiid.jboss.EventDistributorFactoryService.start(EventDistributorFactoryService.java:41) [teiid-jboss-integration-8.2.0.Final.jar:8.2.0.Final]
              [Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
              [Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
              [Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_25]
              [Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_25]
              [Server:server-one]     at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_25]
              [Server:server-one] Caused by: java.net.BindException: bind_addr /0.0.0.0 is not a valid interface: java.net.BindException: Address already in use
              [Server:server-one]     at org.jgroups.util.Util.createServerSocket(Util.java:3181) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.FD_SOCK.startServerSocket(FD_SOCK.java:562) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:299) [jgroups-3.0.6.Final.jar:3.0.6.Final]
              [Server:server-one]     ... 22 more

              • 4. Re: Cannot bind the domain controller to 0.0.0.0
                Alexis Hassler Apprentice

                Hi Jose,

                 

                I've just (re) with a regular JBoss AS 7.1.1 and it's working like a charm.

                 

                In you're logs, I'm seeing that you're using Teiid, in a cluster configuration. And the issue seems to come from a cluster binding. The last message says "java.net.BindException: Address already in use" which means that you have a conflict on a particular port. Unfortunatly, the stacktrace doesn't say which port .

                 

                You should have a look on netstat to seek the port.

                • 5. Re: Cannot bind the domain controller to 0.0.0.0
                  Jose Chavez Newbie

                  Hello Alexis,

                   

                  Yes, I tried pure JBOSS AS and it did work. I do in fact, have Teiid installed over JBOSS and that is the problem. I tracked down the port in question and it seems to be the remoting service running on port 4447. I guess I need to open a discussion on the Teiid product category...

                  • 6. Re: Cannot bind the domain controller to 0.0.0.0
                    Alexis Hassler Apprentice

                    A port offset could solve your problem. You should have a look at the wiki page called "Multiple instances of JBoss AS7 on the same machine"

                    • 7. Re: Cannot bind the domain controller to 0.0.0.0
                      Ramesh Reddy Master

                      Could this be same as this

                       

                      http://permalink.gmane.org/gmane.comp.java.javagroups.general/7257

                       

                      this root message is

                       

                      Caused by: java.net.BindException: bind_addr /0.0.0.0 is not a valid interface: java.net.BindException: Address already in use

                       

                      There is nothing Teiid does special other than depend on a ChannelFactory service from jgroups subsystem.

                       

                      Ramesh..

                      • 8. Re: Cannot bind the domain controller to 0.0.0.0
                        Vladislav Rames Newbie

                        Hello,

                         

                        I also got the same error message, Jboss AS 7.1.1 on RHEL 6.4 - problem was missing or wrong record in /etc/hosts.

                        Quite confusing reason (for me).

                         

                        Best Regards

                         

                        Vladislav