You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (Assigned) (JIRA)" <ji...@apache.org> on 2012/03/11 20:16:37 UTC

[jira] [Assigned] (QPID-3879) Session#close() on session can produce spurious "dispatcher is not started" messages at ERROR to client logs

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

Keith Wall reassigned QPID-3879:
--------------------------------

    Assignee: Robbie Gemmell  (was: Keith Wall)
    
> Session#close() on session can produce spurious "dispatcher is not started" messages at ERROR 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.10, 0.12, 0.14, 0.16
>            Reporter: Keith Wall
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.17
>
>
> 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 consume 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org