You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/09/21 18:05:16 UTC
[jira] Commented: (QPID-2111) SelectorTest is split into two and
doesn't test runtime selector exceptions
[ https://issues.apache.org/jira/browse/QPID-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757937#action_12757937 ]
Martin Ritchie commented on QPID-2111:
--------------------------------------
The java client does not behave in the same way when run with the CPP broker and java Broker.
The java broker has server side filtering and closes the connection on the erroneous consume.
The cpp broker does no filtering but the client throws an exception that is never reported.
I don't think either are write. The consumer should not be penalised by the erroneous publisher, so the connection should stay open, but the client should receive an exception. Ideally the publisher should to but that is much harder!
> SelectorTest is split into two and doesn't test runtime selector exceptions
> ---------------------------------------------------------------------------
>
> Key: QPID-2111
> URL: https://issues.apache.org/jira/browse/QPID-2111
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: 0.6
> Reporter: Aidan Skinner
> Assignee: Aidan Skinner
> Priority: Minor
> Fix For: 0.6
>
>
> SelectorTest exists in two places and only tests parse-time selector errors, not if a runtime error occurs such as trying a mathmatical operation on a string property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org