activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-3616) SchedulerBroker creates persistent messages even when broker.persistent=false is specified
Date Thu, 15 Dec 2011 21:55:31 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-3616.
-----------------------------

    Resolution: Not A Problem

Working as designed, the scheduled broker support currently only knows how to store the future
messages in a persistent manner so that they aren't lost on broker shutdown.  
                
> SchedulerBroker creates persistent messages even when broker.persistent=false is specified
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3616
>                 URL: https://issues.apache.org/jira/browse/AMQ-3616
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.1
>         Environment: java 1.6.0_26, MacOS X 10.7.2
>            Reporter: Thomas Krammer
>
> For unit tests I try to create a in-memory JMS connection like this:
> final ActiveMQConnectionFactory connectionFactory = new ActiveMQConnectionFactory("vm://localhost?broker.persistent=false&broker.schedulerSupport=true");
> connection = connectionFactory.createConnection();
> When "broker.schedulerSupport=true" is specified all scheduled messages are store in
a persistent storage even though "broker.persistent" is false.

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