qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3978) Broker should remove messages with expired TTL even if they are prefetched by the client
Date Thu, 14 Aug 2014 22:49:19 GMT

    [ https://issues.apache.org/jira/browse/QPID-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097847#comment-14097847
] 

Rob Godfrey commented on QPID-3978:
-----------------------------------

Hmmm  - OK, I'll look into this - this was with AUTO-ACK?

> Broker should remove messages with expired TTL even if they are prefetched by the client
> ----------------------------------------------------------------------------------------
>
>                 Key: QPID-3978
>                 URL: https://issues.apache.org/jira/browse/QPID-3978
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: 0.10, 0.12, 0.14
>            Reporter: Alex Rudyy
>            Assignee: Rob Godfrey
>             Fix For: 0.31
>
>
> Broker should remove messages with expired TTL even if they are prefetched by the client.
> If client application prefetches the messages and hangs, the messages with expired TTL
are remained on broker till client is closed or killed.
> The prefetched messages with expired TTL can cause a lot of confusions to the end users.
It would be better to remove them on the broker after  TTL is expired without waiting for
acknowledgment/releasing them from a client.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message