Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 30 Sep 2011 21:17:46 +0000 (UTC)
From: "Timothy Bish (Closed) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <561893122.13384.1317417466994.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (AMQ-2445) Repeating NPE on shutdown under Tomcat
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish closed AMQ-2445.
-----------------------------

    Resolution: Cannot Reproduce

No test case available.   Suggest testing with a current release of the broker.
                
> 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.x
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira