We found that activemq with postgresql persistance backend opens a connection, starts a transaction and waits forever. Due to this reason (extremely long lasting transaction ) all our 'vacuuming DB' fail. Therefore all DB on that postgresql server became very slow.
Does anyone know how to force activemq to open transaction only when it's needed or at least to restart that 'idle in transaction' after some time of inactivity? Thanks in advance Alex -- View this message in context: http://www.nabble.com/%27idle-in-transaction%27-open-connection-problems-tf3982025s2354.html#a11304454 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
