You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2012/08/27 11:59:07 UTC

[jira] [Created] (APLO-249) Message expiration does not (always) work on topics

Lionel Cons created APLO-249:
--------------------------------

             Summary: Message expiration does not (always) work on topics
                 Key: APLO-249
                 URL: https://issues.apache.org/jira/browse/APLO-249
             Project: ActiveMQ Apollo
          Issue Type: Bug
         Environment: apollo-99-trunk-20120826.223050-99
            Reporter: Lionel Cons


When Apollo receives an already expired message for a topic that has subscribers, its behavior depends on the topic configuration:
 - with slow_consumer_policy="queue", the message is not delivered
 - with slow_consumer_policy="block", the message is delivered

I would have expected the message to be dropped regardless of the topic configuration.

--
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

[jira] [Resolved] (APLO-249) Message expiration does not (always) work on topics

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-249.
--------------------------------

    Resolution: Fixed

Next nightly snapshot should fix this.
                
> Message expiration does not (always) work on topics
> ---------------------------------------------------
>
>                 Key: APLO-249
>                 URL: https://issues.apache.org/jira/browse/APLO-249
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-stomp
>    Affects Versions: 1.4
>         Environment: apollo-99-trunk-20120826.223050-99
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>
> When Apollo receives an already expired message for a topic that has subscribers, its behavior depends on the topic configuration:
>  - with slow_consumer_policy="queue", the message is not delivered
>  - with slow_consumer_policy="block", the message is delivered
> I would have expected the message to be dropped regardless of the topic configuration.

--
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

[jira] [Updated] (APLO-249) Message expiration does not (always) work on topics

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-249:
-------------------------------

          Component/s: apollo-stomp
    Affects Version/s: 1.4
        Fix Version/s: 1.5
             Assignee: Hiram Chirino
    
> Message expiration does not (always) work on topics
> ---------------------------------------------------
>
>                 Key: APLO-249
>                 URL: https://issues.apache.org/jira/browse/APLO-249
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-stomp
>    Affects Versions: 1.4
>         Environment: apollo-99-trunk-20120826.223050-99
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>
> When Apollo receives an already expired message for a topic that has subscribers, its behavior depends on the topic configuration:
>  - with slow_consumer_policy="queue", the message is not delivered
>  - with slow_consumer_policy="block", the message is delivered
> I would have expected the message to be dropped regardless of the topic configuration.

--
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