[jboss-jira] [JBoss JIRA] Resolved: (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:all-tabpanel ]

Yong Hao Gao resolved JBMESSAGING-1844.
---------------------------------------

    Resolution: Done


Add a check in ServerConsumerEndpoint and ClientConsumer so that expired messages won't get processed by the suckers.


> 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, 1.4.0.SP3.CP14, 1.4.8.SP2
>         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, 1.4.8.SP3
>
>         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