7 Replies Latest reply on Apr 14, 2014 2:55 PM by James Perkins

    Deployment by maven

    Times times Newbie

      Hello,

       

      Am trying to do a remote deploy on our server (standalone full) but it fails with:

       

      java.net.ConnectException: JBAS012144: Could not connect to remote://192.*.*.*:9999. The connection timed out

      Caused by: java.lang.IllegalStateException: Error could not execute operation '{

          "address" => [],

          "operation" => "read-attribute",

          "name" => "launch-type"

      }'.

              at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:186)

              at org.jboss.as.plugin.common.AbstractServerConnection.getClient(AbstractServerConnection.java:132)

              at org.jboss.as.plugin.common.AbstractServerConnection.isDomainServer(AbstractServerConnection.java:109)

              at org.jboss.as.plugin.deployment.AbstractDeployment.validate(AbstractDeployment.java:187)

              at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:146)

       

      my pom.xml:

      <plugin>

          <groupId>org.jboss.as.plugins</groupId>

             <artifactId>jboss-as-maven-plugin</artifactId>

             <version>7.5.Final</version>

           <configuration>                         

              <hostname>192.*.*.*</hostname>

              <port>9999</port>

              <username>user</username>

              <password>secret</password>

              <filename>${project.build.finalName}.ear</filename>                         

          </configuration>

          <executions>

              <execution>

                  <phase>verify</phase>

                  <goals>

                      <goal>deploy</goal>

                  </goals>

              </execution>

          </executions>

      </plugin>

       

      My standalone-full.xml is same as out of the box, the key entries been:

      a) <subsystem xmlns="urn:jboss:domain:jmx:1.1">

                  <show-model value="true"/>

                  <remoting-connector use-management-endpoint="false"/>

      </subsystem>

       

      b) <interfaces>

              <interface name="management">

                  <any-ipv4-address/>

              </interface>

              <interface name="public">

                  <inet-address value="${jboss.bind.address:127.0.0.1}"/>

              </interface>

              <interface name="unsecure">

                  <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>

              </interface>

      </interfaces>

       

      c)

          <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

       

      Also I can Telnet from my local machine to the remote on port 9999 and these are the ports on the remote server where jboss is running:

      Proto      Local Address Foreign AddressState
      tcp    0.0.0.0:5455            0.0.0.0:*               LISTEN
      tcp    0.0.0.0:9999            0.0.0.0:*               LISTEN
      tcp    0.0.0.0:111             0.0.0.0:*               LISTEN
      tcp    0.0.0.0:8080            0.0.0.0:*               LISTEN
      tcp    0.0.0.0:22              0.0.0.0:*               LISTEN
      tcp    0.0.0.0:4447            0.0.0.0:*               LISTEN
      tcp    0.0.0.0:5445            0.0.0.0:*               LISTEN
      tcp    0.0.0.0:9990            0.0.0.0:*               LISTEN
      tcp    0.0.0.0:37191           0.0.0.0:*               LISTEN
      tcp    127.0.0.1:3528          0.0.0.0:*               LISTEN
      tcp    192.*.*.*:22        192.*.*.79:63248     ESTABLISHED
      tcp    192.*.*.*:22        192.*.*.65:59411     ESTABLISHED
      tcp    192.*.*.*:22        192.*.*.65:55127     ESTABLISHED
      tcp    192.*.*.*:22        192.*.*.65:59409     ESTABLISHED
      tcp    192.*.*.*:22        192.*.*.79:63273     ESTABLISHED
      tcp    192.*.*.*:9999      192.*.*.79:63272     ESTABLISHED
      tcp    192.*.*.*:22        192.*.*.79:61862     ESTABLISHED

       

      Can please someone let me know what's going wrong.

       

      Thanks,

        • 1. Re: Deployment by maven
          Wolf-Dieter Fink Master

          Did you bind the management interface direct to 192.* or use 0.0.0.0? If yes what if you use the real ip?

          • 2. Re: Deployment by maven
            Times times Newbie

            Thanks for your reply.

            Am a bit new to JBoss, do you mean the configuration on the standalone-full.xml:

             

            <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

            <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>

            <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>

             

            I've kept it as it is i.e. the default ones.

            Also I've noticed that I cannot connect to the server through a JConsole client if it helps.   

            • 3. Re: Deployment by maven
              Times times Newbie

              This is my interfaces:

               

              <interfaces>

                      <interface name="management">

                          <any-ipv4-address/>

                      </interface>

                      <interface name="public">

                          <inet-address value="${jboss.bind.address:127.0.0.1}"/>

                      </interface>

                      <interface name="unsecure">

                          <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>

                      </interface>

                  </interfaces>

               

              I also tried changing the above to

              <interfaces>

                      <interface name="management">

                          <any/>

                      </interface>

                  </interfaces>

               

              But still doesn't work!

               

              Additionally am trying to remote connect it through jconsole but can't connect it either:

              service:jmx:remoting-jmx://192.*.*.*:9999

               

              Any experts out there ?

              Thanks.

              • 4. Re: Deployment by maven
                Wolf-Dieter Fink Master

                You should set the ip address direct, the original entry for management is

                 

                        <interface name="management">

                            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>

                        </interface>

                 

                So you can change the 127.0.0.1 to the real IP address of your server and then you should able to use it

                • 5. Re: Deployment by maven
                  Times times Newbie

                  Thanks for your prompt response but it still doesnt help:

                          <interface name="management">

                              <inet-address value="192.*.*.*"/>

                          </interface>

                     

                  Not sure what else, perhaps that's why I can't connect through jconsole either. Everything is been converted to 'remoting'.

                   

                  Any other ideas?

                  • 6. Re: Deployment by maven
                    Wolf-Dieter Fink Master

                    Don't understand whats wrong.

                     

                    Could you use a fresh unpacked server and try maven on the same host, in that case localhost is used.

                    If that works start standalone.sh -bmanagement 192.*.*.* -b 192.*.*.*

                    You should be able to access the welcome page at 8080 with your browser and use jboss-cli.sh --controller=192.*.*.*:9999 and see whether this works

                    • 7. Re: Deployment by maven
                      James Perkins Master

                      Do you have a firewall rule blocking the port? Or most likely do you have a firewall rule enabling port 9999 on your 192.x.x.x address?

                       

                      --

                      James R. Perkins