1 2 Previous Next 26 Replies Latest reply on Apr 25, 2013 11:06 AM by Mauricio Magnani Jr

    erro jboss 7 - Could not connect to remote

    Adriano Schmidt Master

      Do nada..

       

      começou a acontecer esse erro quando tento acessar o cli do meu domain:

       

      [root@SERVER_JBOSS local]# jboss-eap-6.0/bin/jboss-cli.sh -c --controller=192.168.16.133:9999

      org.jboss.as.cli.CliInitializationException: Failed to connect to the controller

              at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:264)

              at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:242)

              at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.modules.Module.run(Module.java:270)

              at org.jboss.modules.Main.main(Main.java:294)

      Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 192.168.16.133:9999

              at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:888)

              at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:727)

              at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:704)

              at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:262)

              ... 8 more

      Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.133:9999. The connection timed out

              at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)

              at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)

              at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:866)

              ... 11 more

      Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.133:9999. The connection timed out

              at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)

              at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:247)

              at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)

              at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)

              at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)

              at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)

              at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)

              at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)

              at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)

              at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)

              at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)

              ... 13 more

      [root@SERVER_JBOSS local]#

       

       

      e o meu servidor tá no ar:

       

       

       

      [root@SERVER_JBOSS_225 ~]# /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/master -Djboss.host.default.config=host-master.xml -Djboss.bind.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.133

      =========================================================================

       

       

        JBoss Bootstrap Environment

       

       

        JBOSS_HOME: /usr/local/jboss-eap-6.0

       

       

        JAVA: /usr/java/jdk1.6.0_33/bin/java

       

       

        JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.domain.default.config=domain.xml -Djboss.host.default.config=host.xml

       

       

      =========================================================================

       

       

      23:04:50,465 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA-redhat-1

      23:04:52,007 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'

      [Host Controller] 23:04:55,399 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA-redhat-1

      [Host Controller] 23:04:56,471 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA-redhat-2

      [Host Controller] 23:04:57,273 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting

      [Host Controller] 23:05:00,705 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1

      [Host Controller] 23:05:00,748 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1

      [Host Controller] 23:05:00,787 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.14.GA-redhat-1

      [Host Controller] 23:05:00,863 INFO  [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)

      [Host Controller] 23:05:01,298 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 192.168.16.133:9999

      [Host Controller] 23:05:13,071 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.16.133:9990/management

      [Host Controller] 23:05:13,072 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.16.133:9990

      [Host Controller] 23:05:13,074 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) (Host Controller) started in 20775ms - Started 11 of 11 services (0 services are passive or on-demand)

      [Host Controller] 23:06:25,471 ERROR [org.jboss.remoting.remote.connection] (Remoting "server_jboss_225:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer

      [Host Controller] 23:09:08,368 INFO  [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "slave01", JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4)

      [Host Controller] 23:11:35,221 INFO  [org.jboss.as.domain] (slave-request-threads - 1) JBAS010918: Registered remote slave host "slave02", JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4)

       

       

       

      Tô tentando acessar da mesma máquina..

       

      não sei pq começou a dar esse erro..

       

      aí fui nos host e tava dando um erro semelhante:

       

      [Server:server-one] 23:09:03,640 INFO  [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting

      [Server:server-one] 23:09:05,642 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1

      [Server:server-one] 23:09:05,979 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1

      [Server:server-one] 23:09:06,215 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.14.GA-redhat-1

      [Server:server-one] 23:10:05,277 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.134:9999. The connection timed out

      [Server:server-one]     at org.jboss.as.server.mgmt.domain.HostControllerServerClient.start(HostControllerServerClient.java:172) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

      [Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

      [Server:server-one]     at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

      [Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

      [Server:server-one]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

      [Server:server-one]     at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

      [Server:server-one] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.134:9999. The connection timed out

      [Server:server-one]     at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120) [jboss-as-protocol-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

      [Server:server-one]     at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:84) [jboss-as-protocol-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

      [Server:server-one]     at org.jboss.as.server.mgmt.domain.HostControllerServerConnection.openChannel(HostControllerServerConnection.java:158) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

      [Server:server-one]     at org.jboss.as.server.mgmt.domain.HostControllerServerConnection.connect(HostControllerServerConnection.java:86) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

      [Server:server-one]     at org.jboss.as.server.mgmt.domain.HostControllerServerClient.start(HostControllerServerClient.java:148) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

      [Server:server-one]     ... 5 more

      [Server:server-one]

       

       

       

      E como isso começou a acontecer do nada não tenho ideia do que possa ser :/

        • 1. Re: erro jboss 7 - Could not connect to remote
          Mauricio Magnani Jr Master

          Oi Adriano,

           

          Tá ocorrendo algum erro de comunicação entre o Domain Controller e Host Controlle.

          Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 192.168.16.133:9999

          Verifica se o firewall está bloqueando a comunição...  utiliza o telnet da seguinte forma para realizar os testes:

           

          telnet 192.168.16.133 9999

           

          Me diz ai se é isso..

           

          Abs

          • 2. Re: erro jboss 7 - Could not connect to remote
            Adriano Schmidt Master

            Fiz o seguinte teste agora, Iniciou o domain (com os dois host parados):

             

            [root@SERVER_JBOSS /]# /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/master -Djboss.host.default.config=host-master.xml -Djboss.bind.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.133

            =========================================================================

             

             

              JBoss Bootstrap Environment

             

             

              JBOSS_HOME: /usr/local/jboss-eap-6.0

             

             

              JAVA: /usr/java/jdk1.6.0_33/bin/java

             

             

              JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.domain.default.config=domain.xml -Djboss.host.default.config=host.xml

             

             

            =========================================================================

             

             

            23:34:57,918 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA-redhat-1

            23:34:58,044 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'

            [Host Controller] 23:34:58,678 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA-redhat-1

            [Host Controller] 23:34:58,814 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA-redhat-2

            [Host Controller] 23:34:59,019 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting

            [Host Controller] 23:34:59,776 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1

            [Host Controller] 23:34:59,781 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1

            [Host Controller] 23:34:59,806 INFO  [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)

            [Host Controller] 23:34:59,886 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.14.GA-redhat-1

            [Host Controller] 23:34:59,935 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 192.168.16.133:9999

            [Host Controller] 23:35:01,850 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.16.133:9990/management

            [Host Controller] 23:35:01,852 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.16.133:9990

            [Host Controller] 23:35:01,854 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) (Host Controller) started in 3735ms - Started 11 of 11 services (0 services are passive or on-demand)

             

            aí na mesma máquina dei um

             

            telnet localhost 9999

             

            como resultado:

             

            Trying 127.0.0.1...

            telnet: connect to address 127.0.0.1: Connection refused

            telnet: Unable to connect to remote host: Connection refused

             

            e ao iniciar o cli:

             

            [root@SERVER_JBOSS local]# jboss-eap-6.0/bin/jboss-cli.sh -c --controller=192.168.16.133:9999

            org.jboss.as.cli.CliInitializationException: Failed to connect to the controller

                    at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:264)

                    at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:242)

                    at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)

                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                    at java.lang.reflect.Method.invoke(Method.java:597)

                    at org.jboss.modules.Module.run(Module.java:270)

                    at org.jboss.modules.Main.main(Main.java:294)

            Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 192.168.16.133:9999

                    at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:888)

                    at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:727)

                    at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:704)

                    at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:262)

                    ... 8 more

            Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.133:9999. The connection timed out

                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)

                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)

                    at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:866)

                    ... 11 more

            Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.133:9999. The connection timed out

                    at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)

                    at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:247)

                    at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)

                    at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)

                    at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)

                    at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:67)

                    at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)

                    at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)

                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)

                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)

                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)

                    ... 13 more

             

            firewall a princípio não é:

             

            [root@SERVER_JBOSS local]# iptables -L

            Chain INPUT (policy ACCEPT)

            target     prot opt source               destination        

             

             

            Chain FORWARD (policy ACCEPT)

            target     prot opt source               destination        

             

             

            Chain OUTPUT (policy ACCEPT)

            target     prot opt source               destination    

             

            não sei :/

            • 3. Re: erro jboss 7 - Could not connect to remote
              Adriano Schmidt Master

              e o console web eu consigo acessar pelo http://192.168.16.133:9990

               

              então o jboss tá no ar..

              • 4. Re: erro jboss 7 - Could not connect to remote
                Mauricio Magnani Jr Master

                Adriano,

                 

                Acredito que na sua inicialização esteja faltando:

                 

                 

                -Djboss.bind.address.management=192.168.16.133

                 

                Abs

                • 5. Re: erro jboss 7 - Could not connect to remote
                  Mauricio Magnani Jr Master

                  Faz o seguinte só coloca os parametros de inicialização do master e host controller... ai podemos verificar o que pode estar ocorrendo.

                  • 6. Re: erro jboss 7 - Could not connect to remote
                    Adriano Schmidt Master

                    Acredito que na sua inicialização esteja faltando:

                     

                     

                    -Djboss.bind.address.management=192.168.16.133

                     

                    minha inicialização tá assim:

                    /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/master -Djboss.host.default.config=host-master.xml -Djboss.bind.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.133

                     

                     

                     

                    sobre isso:

                     

                    Faz o seguinte só coloca os parametros de inicialização do master e host controller... ai podemos verificar o que pode estar ocorrendo.

                     

                    não entendi.. tirar os dois -D[..]bind[..] ?

                    • 7. Re: erro jboss 7 - Could not connect to remote
                      Mauricio Magnani Jr Master

                      hehehe eu quis dizer para colocar todos os parametros utilizados do master e todos parametros utilizado no host controller.

                      • 8. Re: erro jboss 7 - Could not connect to remote
                        Adriano Schmidt Master

                        colocar aqui? hahah

                         

                        segue:

                         

                        master:

                         

                        /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/master -Djboss.host.default.config=host-master.xml -Djboss.bind.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.133

                         

                        slave01:

                         

                        /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/slave01 -Djboss.host.default.config=host-slave.xml -Djboss.domain.master.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.134 -Djboss.bind.address=192.168.16.134 -Djboss.server.name=server-one

                         

                        slave02:

                         

                        /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/slave02 -Djboss.host.default.config=host-slave.xml -Djboss.domain.master.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.135 -Djboss.bind.address=192.168.16.135 -Djboss.server.name=server-two

                         

                         

                        mas o erro ali em cima do CLI tá acontecendo enquanto os slave01 e o slave02 tão parados...

                        • 9. Re: erro jboss 7 - Could not connect to remote
                          Mauricio Magnani Jr Master

                          hum...

                           

                          Vamos deixar claro a situação então....

                           

                          A unica coisa que está de pé o o Domain Controller (master) ?

                           

                          O slave01 e slave2 estão parados?

                           

                          Abs

                          • 10. Re: erro jboss 7 - Could not connect to remote
                            Adriano Schmidt Master

                            isso... aí quando eu tento iniciar o CLI tá dando esse erro:

                             

                            [root@SERVER_JBOSS local]# jboss-eap-6.0/bin/jboss-cli.sh -c --controller=192.168.16.133:9999

                            org.jboss.as.cli.CliInitializationException: Failed to connect to the controller

                                    at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:264)

                                    at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:242)

                                    at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)

                                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

                                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                                    at java.lang.reflect.Method.invoke(Method.java:597)

                                    at org.jboss.modules.Module.run(Module.java:270)

                                    at org.jboss.modules.Main.main(Main.java:294)

                            Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at 192.168.16.133:9999

                                    at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:888)

                                    at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:727)

                                    at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:704)

                                    at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:262)

                                    ... 8 more

                            Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.133:9999. The connection timed out

                                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)

                                    at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)

                                    at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:866)

                                    ... 11 more

                            Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://192.168.16.133:9999. The connection timed out

                                    at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)

                                    at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:247)

                                    at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)

                             

                             

                            mas caso eu startasse o slave01 daria um erro parecido.. mas enfim.. com ele parado dá erro ao iniciar o CLI...

                             

                            vamo lá..

                             

                            apache iniciado...

                            domain iniciado...

                            slave01 parado..

                            slave02 parado...

                             

                            segue abaixo log de inicialização do domain:

                             

                            [jboss@SERVER_JBOSS /]$ /usr/local/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss-eap-6.0/master -Djboss.host.default.config=host-master.xml -Djboss.bind.address=192.168.16.133 -Djboss.bind.address.management=192.168.16.133

                            =========================================================================

                             

                             

                              JBoss Bootstrap Environment

                             

                             

                              JBOSS_HOME: /usr/local/jboss-eap-6.0

                             

                             

                              JAVA: /usr/java/jdk1.6.0_33/bin/java

                             

                             

                              JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.domain.default.config=domain.xml -Djboss.host.default.config=host.xml

                             

                             

                            =========================================================================

                             

                             

                            23:51:13,534 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA-redhat-1

                            23:51:13,701 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'

                            [Host Controller] 23:51:14,382 INFO  [org.jboss.modules] (main) JBoss Modules version 1.1.3.GA-redhat-1

                            [Host Controller] 23:51:14,522 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA-redhat-2

                            [Host Controller] 23:51:14,728 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting

                            [Host Controller] 23:51:15,441 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1

                            [Host Controller] 23:51:15,446 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1

                            [Host Controller] 23:51:15,454 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.14.GA-redhat-1

                            [Host Controller] 23:51:15,483 INFO  [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)

                            [Host Controller] 23:51:15,595 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 192.168.16.133:9999

                            [Host Controller] 23:51:17,409 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.16.133:9990/management

                            [Host Controller] 23:51:17,410 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.16.133:9990

                            [Host Controller] 23:51:17,410 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) (Host Controller) started in 3590ms - Started 11 of 11 services (0 services are passive or on-demand)

                             

                             

                            aí quando eu tento acessar via CLI dá aquele erro lá de cima.. e no console do domain aparece:

                             

                            [Host Controller] 23:52:06,288 ERROR [org.jboss.remoting.remote.connection] (Remoting "server_jboss_225:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer

                            • 11. Re: erro jboss 7 - Could not connect to remote
                              Adriano Schmidt Master

                              o log do domain não tá muito pequeno? eu lembro q ele era maior..

                               

                              e ela fala só isso da porta 9999:

                               

                              [Host Controller] 23:51:15,595 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 192.168.16.133:9999

                               

                              tá certo ou tá faltando algo na inicialização?

                               

                              talvez sempre foi pequeno e eu to confundindo.. não sei...

                              • 12. Re: erro jboss 7 - Could not connect to remote
                                Mauricio Magnani Jr Master

                                hum sempre foi pequeno mesmo.... eu vou tentar simular aqui mas vai demorar um pouquinho to com um problema na VM

                                 

                                Se segurar as pontas ai... rsrs

                                • 13. Re: erro jboss 7 - Could not connect to remote
                                  Adriano Schmidt Master

                                  bele.. tô pesquisando aqui pra ver se encontro algo..

                                  • 14. Re: erro jboss 7 - Could not connect to remote
                                    Mauricio Magnani Jr Master

                                    Cara o engraçado que acabei de simular aqui.... e work like a charm....

                                     

                                    Inicialização:

                                     

                                    [jboss@localhost /]$ ./usr/local/jboss/7.1.3/jboss-eap-6.0/bin/domain.sh -Djboss.domain.base.dir=/usr/local/jboss/7.1.3/jboss-eap-6.0/master -Djboss.host.default.config=host-master.xml -Djboss.bind.address=192.168.0.127 -Djboss.bind.address.management=192.168.0.127

                                     

                                    Logs

                                     

                                    [Host Controller] 00:16:27,126 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) (Host Controller) started in 11410ms - Started 11 of 12 services (1 services are passive or on-demand)

                                     

                                     

                                    [jboss@localhost /]$ ./usr/local/jboss/7.1.3/jboss-eap-6.0/bin/jboss-cli.sh -c --controller=192.168.0.127:9999

                                    Authenticating against security realm: ManagementRealm

                                    Username: jboss

                                    Password:

                                    [domain@192.168.0.127:9999 /]

                                     

                                     

                                    Não será um problema de rede ou de firewall?

                                     

                                    Abs

                                    1 2 Previous Next