You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/12/02 14:11:04 UTC

[jira] Updated: (AMQ-2445) Repeating NPE on shutdown under Tomcat

     [ https://issues.apache.org/jira/browse/AMQ-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac updated AMQ-2445:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> Repeating NPE on shutdown under Tomcat
> --------------------------------------
>
>                 Key: AMQ-2445
>                 URL: https://issues.apache.org/jira/browse/AMQ-2445
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.2.0
>            Reporter: Brian Topping
>             Fix For: 5.5.0
>
>
> When AMQ is embedded in Tomcat 6 with the vm: connector, the following exception is occasionally produced in large quantity:
> Exception in thread "Persistence Adaptor Task" 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:289)
> 	at org.apache.commons.logging.impl.Log4JLogger.isDebugEnabled(Log4JLogger.java:299)
> 	at org.apache.activemq.store.amq.AMQPersistenceAdapter.doCheckpoint(AMQPersistenceAdapter.java:380)
> 	at org.apache.activemq.store.amq.AMQPersistenceAdapter$1.iterate(AMQPersistenceAdapter.java:237)
> 	at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122)
> 	at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:637)
> It seems to happen more reliably when there are messages that have been transactionally rolled back to the queue over the course of the execution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.