Session#close() on session can produce spurious "dispatcher is not started" at
ERROR messages to client logs
------------------------------------------------------------------------------------------------------------
Key: QPID-3879
URL: https://issues.apache.org/jira/browse/QPID-3879
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.14, 0.12, 0.10
Reporter: Keith Wall
Assignee: Keith Wall
Priority: Minor
Fix For: Future
Calling Session#close() on a session which is still in the process of receiving
messages can result in the following error message to the client log:
{code}
Dispatcher-Channel-1 2012-01-25 22:44:25,298 ERROR
[apache.qpid.thread.LoggingUncaughtExceptionHandler] Uncaught exception in
thread "Dispatcher-Channel-1"
java.lang.IllegalStateException: dispatcher is not started
at org.apache.qpid.client.AMQSession.dispatch(AMQSession.java:3192)
at
org.apache.qpid.client.message.UnprocessedMessage.dispatch(UnprocessedMessage.java:55)
at
org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:3349)
at java.lang.Thread.run(Thread.java:680)
{code}
The problem is longstanding issue, but has probably become more noticeable
since QPID-1670 which introduced a uncaught exception handle that directs such
errors to SLF4J (rather than stderr). Our tests in general don't show the
issue because they tend to consumer all the tests message.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
