[
https://issues.apache.org/jira/browse/AMQ-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623833#comment-13623833
]
Timothy Bish commented on AMQ-4440:
-----------------------------------
Take a closer look at your code, the second message send is setting the string
property on the original message msg1 instead of msg2
> Consumer stuck after failover if selector is present
> ----------------------------------------------------
>
> Key: AMQ-4440
> URL: https://issues.apache.org/jira/browse/AMQ-4440
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.8.0
> Reporter: Denis Bazhenov
> Attachments: Generator.java
>
>
> When selector is used on consumer, consumer stops receiving messages from
> queue after restoring connection to a broker (using failover transport).
> I was able to reproduce situation in the simple environment (one consumer and
> one producer). The main method never terminates if any selector is present on
> the consumer (line 40 of the test application). JMS shows that message is in
> the queue, but for some reason it's not dispatched to the consumer.
--
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
