[
https://issues.apache.org/jira/browse/AMQ-3852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3852.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Fix applied in trunk along with a test case.
> 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
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.7.0
>
>
> 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
