[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1372) Expired message behavior is inconsistent with Topic

Tim Fox (JIRA) jira-events at lists.jboss.org
Mon Sep 22 04:45:22 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox closed JBMESSAGING-1372.
--------------------------------

    Fix Version/s: Unscheduled
                       (was: 1.4.1.GA)
                       (was:  1.4.0.SP3.CP04)
       Resolution: Rejected


This is a non issue.

With a non durable topic subscription, messages are effectively acked before delivery, so on expiry driven from the client, the message is already acked anyway so nothing to do.

> Expired message behavior is inconsistent with Topic
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-1372
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1372
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.4.0.SP3.CP02
>            Reporter: Takayoshi Kimura
>            Assignee: Tim Fox
>             Fix For: Unscheduled
>
>
> A message expired before transferring to client will go to ExpiryQueue.
> A message expired just after transferring to client won't go to ExpiryQueue (No cancelDelivery because ConsumerState#isShouldAck() returns false).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list