[
https://issues.apache.org/activemq/browse/AMQ-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62879#action_62879
]
Krishna commented on AMQ-318:
-----------------------------
Looks like this is not possible in latest releases.
Could you please let me know how to configure the Journal's checkpointinterval
in the latest releases? Is it possible? Or any
workaround? We are using 5.4.0 and the config we are using is:
<persistenceFactory>
<journalPersistenceAdapterFactory journalLogFiles="5"
dataDirectory="${basedir}/activemq-data" dataSource="#mysql-ds />
</persistenceFactory>
Any help would be really appreciated.
Thank you.
Krishna
> Allow the journal's checkpoint period to be configurable.
> ---------------------------------------------------------
>
> Key: AMQ-318
> URL: https://issues.apache.org/activemq/browse/AMQ-318
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Message Store
> Affects Versions: 3.0
> Reporter: Hiram Chirino
> Priority: Minor
> Fix For: 3.1
>
> Attachments: activemq.dtd.patch, JournalPersistenceAdapter.java.patch
>
>
> m...@msdservices.com reported on the user list:
> Is the journal's checkpoint periodicity configurable? Looking in
> JournalPersistenceAdapter.java, the answer appears to be no.
> I would like to request that this timing be exposed. While I am comfortable
> with 5 minutes, the people who have to administer the system I am building
> would not be.
> // Do a checkpoint periodically.
> clockTicket = getClockDaemon().executePeriodically(1000 * 60 * 5, new
> Runnable() {
> public void run() {
> checkpoint(false);
> }
> }, false);
> Matt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
