Apparently, i did not release the listener appropriately. I was stopping
connection insteadof closing. Once that was fixed, the problem went way.

lgestrin wrote:
> 
> Hello,
> i am experiencing same problem that was described in this thread
> http://www.nabble.com/active-mq-exceptions-%28when-tomcat-server-is-stopped%29-tf3367534s2354.html#a9369314
> 
> tomcat version 5.5.17
> activemq version 4.1.0
> 
> i am using activemq package to send/recieve messages in webapp - the
> broker is configured as separate service.
> 
> when tomcat stops, in   ~ 1 sec there is an exception in std.out 
> 
> 
> INFO: Stopping Coyote HTTP/1.1 on http-80
> Apr 13, 2007 2:54:04 PM org.apache.catalina.core.AprLifecycleListener
> lifecycleEvent
> INFO: Failed shutdown of Apache Portable Runtime
> Exception in thread "ActiveMQ Transport:
> tcp://MVQAWEB3623/10.9.30.32:61616" java.lang.NullPointerException
>       at org.apache.log4j.LogManager.getLogger(LogManager.java:188)
>       at org.apache.log4j.Logger.getLogger(Logger.java:104)
>       at
> org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283)
>       at
> org.apache.commons.logging.impl.Log4JLogger.isDebugEnabled(Log4JLogger.java:293)
>       at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:85)
>       at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
>       at
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
>       at
> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
>       at
> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>       at
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
>       at java.lang.Thread.run(Thread.java:595)
> Disconnected from server
> 
> I made sure to close all open connections/listeners on appication stop,
> but it had no effect.
> 
> I also copied log4j.properties from activemq distribution to
> WEB-INF/classes but it had no effect.
> 
> webapplication is using commons-logging that wraps log4j - i dont know if
> it can have anything to do with it.
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/activemq-throws-exception-on-tomcat-stop-log4j-related.-tf3574193s2354.html#a9988187
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to