Dispatcher threads are not always killed
----------------------------------------
Key: QPID-609
URL: https://issues.apache.org/jira/browse/QPID-609
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: M2
Environment: Any
Reporter: Robert Greig
Assignee: Robert Greig
When taking a thread dump at random points during the client unit tests there
are huge numbers of dispatcher threads running.
Analysis shows this is because of the potential for dispacher threads to be
created after the session has been closed.
The place where the dispatcher is created is in
AMQSession.confirmConsumerCancelled:
_logger.info("Dispatcher is null so created stopped dispatcher");
startDistpatcherIfNecessary(true);
To see this happening simply run the TopicSessionTest and examine the threads
running after the VMBroker has been shut down.
It is not clear to me why this method could be called *after* a session has
been closed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
