You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/05/21 14:55:41 UTC
[jira] [Commented] (AMQ-3852) Stomp transport allows durable topic
subscriber to subscribe to a queue
[ https://issues.apache.org/jira/browse/AMQ-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280125#comment-13280125 ]
Timothy Bish commented on AMQ-3852:
-----------------------------------
Recommend you create a test case and attach it to demonstrate your issue.
> Stomp transport allows durable topic subscriber to subscribe to a queue
> -----------------------------------------------------------------------
>
> Key: AMQ-3852
> URL: https://issues.apache.org/jira/browse/AMQ-3852
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.5.0
> Reporter: James Green
> Priority: Minor
>
> See also AMQ-2879 the stack-trace to which recently re-emerged in our production logs. The issue was traced to a developer having copy-pasted some PHP script that created a durable topic subscriber but in his clone he subscribed to a queue not a topic. He wasn't to know...
> Question is how to prevent clients getting into this situation. Can the transport disconnect the client and log an error to the console, or must it allow the connection, potentially lulling the client developer into a false sense of functioning code?
> Might also want to review the documentation and potentially the header names to prevent future confusion.
--
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