[
https://issues.apache.org/jira/browse/AMQ-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099691#comment-13099691
]
Jess commented on AMQ-3421:
---------------------------
Actually, the NPE stacktrace is a bit different:
java.lang.NullPointerException
at
org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:510)
at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:105)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:316)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:180)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:69)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:227)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:217)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:199)
at java.lang.Thread.run(Thread.java:736)
> Deadlock when queue fills up
> ----------------------------
>
> Key: AMQ-3421
> URL: https://issues.apache.org/jira/browse/AMQ-3421
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0
> Environment: Tomcat 6.0.29, Spring 3.0.5, Oracle Java 6, Centos 5
> Reporter: Robert Elliot
> Priority: Critical
> Attachments: JStack Output.rtf, jmsMessageQueues.xml
>
>
> We are running a queue to do asynch audit updates, configured via Spring
> 3.0.5.
> When the queue fills up Tomcat locks up with all catalina threads waiting on
> an object monitor in Spring. This object monitor is held by the "ActiveMQ
> Connection Executor: vm://localhost#2986" thread which is itself blocked for
> ever awaiting the stopped CountDownLatch at
> TransportConnection.stop(TransportConnection.java:930).
> There are no "ActiveMQ Task" threads running, which suggests that either the
> task created by stopAsync has completed or did not run.
> A code review leaves us baffled as to how this latch cannot have counted
> down, but it hasn't. Could Tomcat possibly be silently discarding the thread
> that was meant to do the stop without throwing an exception?! It seems
> unlikely but (as I understand it) TaskRunnerFactory is breaking the Servlet
> spec by running up its own Threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
