[
https://issues.apache.org/jira/browse/AMQ-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243546#comment-17243546
]
Matt Pavlovich commented on AMQ-1660:
-------------------------------------
[~robb...@earthlink.net]please update this ticket if this is still an issue
when using ActiveMQ 5.16.0. The JDBC layer has had a number of updates--
specifically, with the
[JDBCLeaseLocker|https://activemq.apache.org/pluggable-storage-lockers]
NOTE: This JIRA is scheduled to close in 30 days if no update is provided.
> Scheduled Failover
> ------------------
>
> Key: AMQ-1660
> URL: https://issues.apache.org/jira/browse/AMQ-1660
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 4.1.1, 5.0.0
> Environment: all platforms that support a running standalone broker
> Reporter: Rob Bugh
> Assignee: Hiram R. Chirino
> Priority: Major
> Fix For: NEEDS_REVIEW
>
>
> I am using a JDBC Master/Slave topology. I'm using Postgres as the db and
> noticed that due to the long running transaction of the master holding the
> lock on the activemq_lock table my vacuums are not cleaning as many dead
> tuples as they could. If you are familiar with postgres then you know that
> vacuum can only recover dead tuples up to the point of the oldest
> transaction. My activemq database is on the same db server as my production
> db.
> So I would like to regularly failover the master to the slave to keep the
> lock transaction timestamp moving forward in time.
> Is there any facility built into activemq that would allow me to schedule a
> restart of a broker? For example, it would be nice to have the ability to
> specify in the broker.xml a TTL value that would mean run for this much time
> then restart yourself (or shutdown).
> Rob
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
