Nothing says that the open transaction is the same transaction at time A and time B; I've been repeatedly unable to truncate a table in Oracle (in an application unrelated to ActiveMQ, but it illustrates the point) because there were lots and lots of transactions per second against the table. As such, your conclusion/assumption that there's a single open transaction that remains open for a long period of time may be inaccurate. (Or it may not, but unless you've got something concrete to prove that the same transaction is alive between the two points in time, I'd assume that's not it.) In either case, I'm not aware of a way to force a running broker to commit any particular database connection.
I'd suggest you contact Blackboard for advice on how to manage their application; they might have a way to suspend the system to allow the broker's database to be cleaned up. Tim On Tue, Sep 6, 2016 at 2:08 AM, alnaimi.ay...@gmail.com < alnaimi.ay...@gmail.com> wrote: > Hi ,we have Blackboard application which use ActiveMQ, it is causing the > database to grew huge in size , we can't truncate because there is always > active transaction. transaction Logs never get cleared out after taking > backup due to an open transaction. , s there any way to force AMQ to > commit > the transaction on a schedule? or what else could be preventing the commit > from happening . > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/ActiveMQ-is-causing-the-database-log-to- > grow-huge-tp4716176.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
