• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
When running aleph_shutdown scripts, jobs/processes seem to be stopping appropriately.
However, sometimes there are what appear to be JBOSS error messages:

Shutting down JBOSS...
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 123.0.0.1:2881
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1198)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.Shutdown.main(Shutdown.java:188)
shutdown complete

Resolution:
This is not technically a problem.
aleph_shutdown sends a shutdown signal to JBOSS, but JBOSS is already down (not started at startup by default).
It can be ignored.

• Article last edited: 10/8/2013