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 (JIRA)" <ji...@apache.org> on 2012/07/19 14:32:33 UTC
[jira] [Created] (QPID-4153) Messages causing a runtime selector
error should be dead-lettered (or something similar)
Keith Wall created QPID-4153:
--------------------------------
Summary: Messages causing a runtime selector error should be dead-lettered (or something similar)
Key: QPID-4153
URL: https://issues.apache.org/jira/browse/QPID-4153
Project: Qpid
Issue Type: Bug
Components: Java Broker
Environment: Test SelectorTest#testRuntimeSelectorError tries to test the case where the contents message header causes the evaluation a consumer's selector to fail with a RuntimeException (most likely due to a type issue). The test goes on to assert that the producer's session (or connection) is closed to single the error.
There is a problem with the whole approach. It is not certain that the producer will still be present when this determination is made. The producer could have already gone away or the message might be being moved to a queue by a management operation etc.
The broker should be changed to handle the scenario in a different manner, such as routing the message to an alternate exchange or dead-letter-queue.
Reporter: Keith Wall
Assignee: Keith Wall
Fix For: Future
--
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-4153) Messages causing a runtime selector
error should be dead-lettered (or something similar)
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4153:
-----------------------------
Description:
Test SelectorTest#testRuntimeSelectorError tries to test the case where the contents message header causes the evaluation a consumer's selector to fail with a RuntimeException (most likely due to a type issue). The test goes on to assert that the producer's session (or connection) is closed to single the error.
There is a problem with the whole approach. It is not certain that the producer will still be present when this determination is made. The producer could have already gone away or the message might be being moved to a queue by a management operation etc.
The broker should be changed to handle the scenario in a different manner, such as routing the message to an alternate exchange or dead-letter-queue.
Environment:
was:
Test SelectorTest#testRuntimeSelectorError tries to test the case where the contents message header causes the evaluation a consumer's selector to fail with a RuntimeException (most likely due to a type issue). The test goes on to assert that the producer's session (or connection) is closed to single the error.
There is a problem with the whole approach. It is not certain that the producer will still be present when this determination is made. The producer could have already gone away or the message might be being moved to a queue by a management operation etc.
The broker should be changed to handle the scenario in a different manner, such as routing the message to an alternate exchange or dead-letter-queue.
> Messages causing a runtime selector error should be dead-lettered (or something similar)
> ----------------------------------------------------------------------------------------
>
> Key: QPID-4153
> URL: https://issues.apache.org/jira/browse/QPID-4153
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment:
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: Future
>
>
> Test SelectorTest#testRuntimeSelectorError tries to test the case where the contents message header causes the evaluation a consumer's selector to fail with a RuntimeException (most likely due to a type issue). The test goes on to assert that the producer's session (or connection) is closed to single the error.
> There is a problem with the whole approach. It is not certain that the producer will still be present when this determination is made. The producer could have already gone away or the message might be being moved to a queue by a management operation etc.
> The broker should be changed to handle the scenario in a different manner, such as routing the message to an alternate exchange or dead-letter-queue.
--
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-4153) Messages causing a runtime selector
error should be dead-lettered (or something similar)
Posted by "Rob Godfrey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455873#comment-13455873 ]
Rob Godfrey commented on QPID-4153:
-----------------------------------
Why is this (causing a RuntimeException) different from simply not matching the selector (when we wouldn't DLQ)? When would a selector cause a runtime error other than type conversion - which should be handled as a non match?
> Messages causing a runtime selector error should be dead-lettered (or something similar)
> ----------------------------------------------------------------------------------------
>
> Key: QPID-4153
> URL: https://issues.apache.org/jira/browse/QPID-4153
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment:
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: Future
>
>
> Test SelectorTest#testRuntimeSelectorError tries to test the case where the contents message header causes the evaluation a consumer's selector to fail with a RuntimeException (most likely due to a type issue). The test goes on to assert that the producer's session (or connection) is closed to single the error.
> There is a problem with the whole approach. It is not certain that the producer will still be present when this determination is made. The producer could have already gone away or the message might be being moved to a queue by a management operation etc.
> The broker should be changed to handle the scenario in a different manner, such as routing the message to an alternate exchange or dead-letter-queue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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