JBoss5.1.0GA shutdown occur error

[michaelfgh]

Hi, all

thanks in advance,
I use the JBoss5.1.0GA atop linux 64-bit (RedHat4.5), I have a issue, when I shutdown the server, it has as follows error in the shutdown log info,

Exception in thread "main" javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: invoker not bound]
 at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1352)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:817)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at org.jboss.Shutdown.main(Shutdown.java:219)
Caused by: javax.naming.NameNotFoundException: invoker not bound
...

and sometimes it has this error

Exception in thread "main" javax.management.RuntimeMBeanException
 at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

so this time shutdown is faild,
I find these information as follows in the jboss/server/default/log directory,

2009-09-04 17:41:58,348 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) Periodic recovery - first pass <Fri, 4 Sep 2009 17:41:58>
2009-09-04 17:41:58,348 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) StatusModule: first pass
2009-09-04 17:41:58,349 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] (Thread-12) [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass
2009-09-04 17:41:58,349 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] (Thread-12) [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
2009-09-04 17:42:08,351 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) Periodic recovery - second pass <Fri, 4 Sep 2009 17:42:08>
2009-09-04 17:42:08,351 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) AtomicActionRecoveryModule: Second pass
2009-09-04 17:42:08,351 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] (Thread-12) [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass
2009-09-04 17:42:08,351 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] (Thread-12) [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass

2009-09-04 17:41:58,348 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) Periodic recovery - first pass <Fri, 4 Sep 2009 17:41:58>
2009-09-04 17:41:58,348 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) StatusModule: first pass
...

2009-09-04 17:42:08,351 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) Periodic recovery - second pass <Fri, 4 Sep 2009 17:42:08>
2009-09-04 17:42:08,351 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] (Thread-12) AtomicActionRecoveryModule: Second pass

..
it repeat these infomation on and on, I think it is incorrect, but I don't know what is its use and why it is repeating, if you have any hint please help me.

Thanks a lot!

[peterj]

The arjuna log entries are the transaction manager running a periodic recovery thread. This is normal operation and you can ignore those log statement. I find those logging statements to be a big enough nuisance that I modify the jboss-log4j.xml file to suppress them.

[michaelfgh]

Thanks Peter,
If these periodic recovery thread log entries is normal, in my application product, when I shutdown the server fastly, my shutdown log has some error, and the shutdown thread is halt. If I shutdown the server after the server start two minutes, it has not any error. So I think the transaction manager running a periodic recovery thread need some time, hence I cannot shutdown the server immediately.
This my understanding, am I correct?
And whether I can modify something to avoid this for shutdown server freely?
Thanks again!

[peterj]

I don't think that the transaction manager thread running has anything to do with the shutdown issues you are citing. I would be more apt to suspect a networking issue - if something in networking is not working correctly the thread doing networking often waits for a timeout.

One way to check for this is to take a thread dump when the app server hangs on shutdown.