Oh, you're trying to truncate the log, not truncate that one table. Sorry
for my confusion.
Gary Tully's comments on https://issues.apache.org/jira/browse/AMQ-2520
show a change you could try in activemq.xml that might allow the
transaction to not stay open. You'll need to apply it to both the m
Thanks for clarifying this transaction.I am trying to truncate it because
it is growing and consuming the space in the log drive and once the drive
is full no more transactions could be made against the database.
On Thu, Sep 8, 2016 at 3:42 PM Tim Bain [via ActiveMQ] <
ml-node+s2283324n4716304...@n
Ah, OK. That transaction is related to the Database Locker (see
http://activemq.apache.org/pluggable-storage-lockers.html), which ensures
that the master broker stays the master as long as it's still alive, and
it's expected to be long-running (and there won't be a way to force it to
complete whil
Thankx Tim,
Actually I can capture what is running against the database in different
time and every time it shows me this:
session_id
Login Name
Database
Begin Time
Log Records
Log Bytes Used
Log Bytes Rsvd
statement_text
Last T-SQL Text
65
db_user
dbname
51:05.5
33097
4104092
71428
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
s
