activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-184) Incorrect handling of default full_drop_policy
Date Tue, 10 Apr 2012 05:55:23 GMT

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

Lionel Cons commented on APLO-184:
----------------------------------

Hmmm... the user manual mentions a "full_policy". Is the manual correct or not?
                
> Incorrect handling of default full_drop_policy
> ----------------------------------------------
>
>                 Key: APLO-184
>                 URL: https://issues.apache.org/jira/browse/APLO-184
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20120404.190241-13
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>
> I've tried the latest snapshot with a config file that does not specify any full_drop_policy.
The config file however does include some destination settings:
>     <!-- destinations only get deleted after one week, topics do not block -->
>     <queue auto_delete_after="604800"/>
>     <topic auto_delete_after="604800" slow_consumer_policy="queue"/>
>     <dsub  auto_delete_after="604800"/>
> Apollo complains with:
> 2012-04-05 07:35:42,781 | WARN  | Invalid 'full_drop_policy' configured for queue 'xxx':
'null' | org.apache.activemq.apollo.broker.Queue | hawtdispatch-DEFAULT-2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message