[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1844) JBM throws "No expiry queue has been specified so the message will be removed"

[Yong Hao Gao (JIRA)]

    [ https://issues.jboss.org/browse/JBMESSAGING-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624000#comment-12624000 ] 

Yong Hao Gao commented on JBMESSAGING-1844:
-------------------------------------------

Hi Tyronne,

With your test program I have successfully reproduced the problem. The cause is that when a consumer receives messages from another node, the messages are first delivered to the sucker's consumer, which 'hijacks' the expired messages. But the sucker's consumer (i.e. remote consumer) doesn't have an expiry queue (and shouldn't have), so it give a warning for each expired message.

Howard


> JBM throws "No expiry queue has been specified so the message will be removed"
> ------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1844
>                 URL: https://issues.jboss.org/browse/JBMESSAGING-1844
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Distributed Support
>    Affects Versions: 1.4.0.SP3.CP10
>         Environment: JBoss-EAP-4.3_CP8, JBM-1.4.0-SP3_CP10
>            Reporter: Tyronne Wickramarathne
>            Assignee: Yong Hao Gao
>             Fix For: 1.4.0.SP3.CP15
>
>         Attachments: DistributedTopicExample.java, test.tar.bz2, TopicReceiver.java
>
>
> Clustered JBM throws "No expiry queue has been specified so the message will be removed" WARN message

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira