Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-3029

jboss_init_redhat script stop feature generates exception

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP 5.0.1.CR1
    • EAP 5.0.0.CR5
    • Consoles
    • None
    • RHEL

    • Release Notes

    Description

      The shell script jboss_init_redhat is used to start and stop a JBoss AS instance, under a given user name.

      To start an EAP instance using the script:

      1. specify location of EAP distribution
        > export JBOSS_HOME=...
      2. specify user name to be used to start instance
        > export JBOSS_USER=...
      3. specify location of Java
        > export JAVAPTH=...
      4. specify the bind address to be used
        > export JBOSS_HOST=...
        > ./jboss_init_redhat start

      To stop an EAP instance using the script:
      > ./jboss_init_redhat stop

      When using a non-loopback bind address, the following exception arises when calling stop:

      [nrla@localhost bin]$ ./jboss_init_redhat.sh stop
      JBOSS_CMD_START = cd /tmp/jboss-eap-5.0/jboss-as/bin; /tmp/jboss-eap-5.0/jboss-as/bin/run.sh -c default -b 192.168.0.100
      Password:
      Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]]
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
      at javax.naming.InitialContext.lookup(InitialContext.java:410)
      at org.jboss.Shutdown.main(Shutdown.java:219)
      Caused by: javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
      ... 4 more
      Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
      ... 5 more
      Caused by: java.net.ConnectException: Connection refused
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:311)
      at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:177)
      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:164)
      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:381)
      at java.net.Socket.connect(Socket.java:569)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
      at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
      ... 5 more

      Attachments

        Issue Links

          Activity

            People

              bshim_jira Brian Shim (Inactive)
              rachmato@redhat.com Richard Achmatowicz
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: