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 (Created) (JIRA)" <ji...@apache.org> on 2012/03/04 12:29:58 UTC
[jira] [Created] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" at ERROR messages to client logs
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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Attachment: (was: 0002-QPID-3879-Session-close-on-session-can-produce-spuri.patch)
> 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
> 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 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
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Attachment: 0001-QPID-3879-MessageListener-test-improvments.patch
> 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
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: Future
>
> Attachments: 0001-QPID-3879-MessageListener-test-improvments.patch, 0002-QPID-3879-Session-close-on-session-can-produce-spuri.patch
>
>
> 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
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Attachment: 0002-QPID-3879-Session-close-on-session-can-produce-spuri.patch
> 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
> Reporter: Keith Wall
> Assignee: Keith Wall
> Priority: Minor
> Fix For: Future
>
> Attachments: 0001-QPID-3879-MessageListener-test-improvments.patch, 0002-QPID-3879-Session-close-on-session-can-produce-spuri.patch
>
>
> 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
[jira] [Assigned] (QPID-3879) Session#close() on session can
produce spurious "dispatcher is not started" messages at ERROR to client
logs
Posted by "Keith Wall (Assigned) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (QPID-3879) Session#close() on session can
produce spurious "dispatcher is not started" messages at ERROR to client
logs
Posted by "Robbie Gemmell (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3879.
----------------------------------
Resolution: Fixed
Looks ok to me.
> 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
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Affects Version/s: 0.16
Fix Version/s: (was: Future)
0.17
Commit applied. Robbie, would you mind reviewing please?
> 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: Keith Wall
> 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
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Description:
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.
was:
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.
> 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
> 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 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
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Summary: Session#close() on session can produce spurious "dispatcher is not started" messages at ERROR to client logs (was: Session#close() on session can produce spurious "dispatcher is not started" at ERROR messages to client logs)
> 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
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Attachment: (was: 0001-QPID-3879-MessageListener-test-improvments.patch)
> 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
> 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 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
[jira] [Commented] (QPID-3879) Session#close() on session can
produce spurious "dispatcher is not started" messages at ERROR to client
logs
Posted by "Keith Wall (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221863#comment-13221863 ]
Keith Wall commented on QPID-3879:
----------------------------------
There is a race between the Dispatcher thread and the thread calling Session#close() (which resets to the reference to the dispatcher within #closeConsumers()).
{code:title=AMQSession$Dispatcher.java}
while (!_closed.get() && ((disp = (Dispatchable) _queue.take()) != null))
{
disp.dispatch(AMQSession.this);
}
{code}
In the above, the LHS of the while expression checks the Dispatcher is not closed, then the RHS blocks until a message arrive. This allows the possibility that that the Dispatcher#close() could have been called (and its reference nulled) by the time the take() returns. In the unlucky case, a message is added to the dispatch queue and AMQSession#close() occurs, causing the IllegalStateException further down the delivery path.
The impact on the end-user application is minimal. As the session is being closed, the Broker will ensure that any unack'd messages will be redelivered. However, the error message will cause confusion to our users.
> 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
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-3879) Session#close() on session can produce
spurious "dispatcher is not started" messages at ERROR to client logs
Posted by "Keith Wall (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-3879:
-----------------------------
Status: Ready To Review (was: In Progress)
> 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: Keith Wall
> 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