You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Rik Gruwez <ri...@admb.be> on 2009/04/07 15:47:20 UTC

Lots of XA transactions going on for no apparent reason

I have setup a transactional message listener in Spring, using ActiveMQ and
Atomikos for JTA. ActiveMQ uses MySQL for persistency, no journaling is
done. I noticed that the ID field in the activemq_msgs table increases for
no apparent reason, without messages being posted on the queues. I enabled
debug logging for ActiveMQ and noticed this:

DEBUG [apache.activemq.TransactionContext] Start:
172.16.203.64.tm0045200059172.16.203.64.tm455
DEBUG [apache.activemq.TransactionContext] Started XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
DEBUG [apache.activemq.TransactionContext] End:
172.16.203.64.tm0045200059172.16.203.64.tm455
DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
DEBUG [apache.activemq.TransactionContext] Commit:
172.16.203.64.tm0045200059172.16.203.64.tm455
DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
DEBUG [apache.activemq.TransactionContext] Start:
172.16.203.64.tm0045300059172.16.203.64.tm456
DEBUG [apache.activemq.TransactionContext] Started XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
DEBUG [apache.activemq.TransactionContext] End:
172.16.203.64.tm0045300059172.16.203.64.tm456
DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
DEBUG [apache.activemq.TransactionContext] Commit:
172.16.203.64.tm0045300059172.16.203.64.tm456
DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
DEBUG [apache.activemq.TransactionContext] Start:
172.16.203.64.tm0045400059172.16.203.64.tm457
DEBUG [apache.activemq.TransactionContext] Started XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
DEBUG [apache.activemq.TransactionContext] End:
172.16.203.64.tm0045400059172.16.203.64.tm457
DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
DEBUG [apache.activemq.TransactionContext] Commit:
172.16.203.64.tm0045400059172.16.203.64.tm457
DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
DEBUG [apache.activemq.TransactionContext] Start:
172.16.203.64.tm0045500059172.16.203.64.tm458
DEBUG [apache.activemq.TransactionContext] Started XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
DEBUG [apache.activemq.TransactionContext] End:
172.16.203.64.tm0045500059172.16.203.64.tm458
DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
DEBUG [apache.activemq.TransactionContext] Commit:
172.16.203.64.tm0045500059172.16.203.64.tm458
DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538

And this keeps going on. Any idea what is causing this?

Regards,
Rik Gruwez

-- 
View this message in context: http://www.nabble.com/Lots-of-XA-transactions-going-on-for-no-apparent-reason-tp22929377p22929377.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Lots of XA transactions going on for no apparent reason

Posted by Gary Tully <ga...@gmail.com>.
and there is the checkpoint/cleanup task that writes a checkpoint record and
deletes old messages. I guess that delete statement is executed irrespective
if there are old messages or not.

I had debug logging going on a deployment and saw:
2009-04-17 11:59:59,599 [ce Adaptor Task] DEBUG
JournalPersistenceAdapter      - Checkpoint started.
2009-04-17 11:59:59,599 [ce Adaptor Task] DEBUG
JDBCPersistenceAdapter         - Cleaning up old messages.
2009-04-17 11:59:59,599 [ce Adaptor Task] DEBUG
DefaultJDBCAdapter             - Executing SQL: DELETE FROM ACTIVEMQ_MSGS
WHERE ( EXPIRATION<>0 AND EXPIRATION<?) OR ID <= ( SELECT
min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM ACTIVEMQ_ACKS WHERE
ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)
2009-04-17 11:59:59,601 [ce Adaptor Task] DEBUG
DefaultJDBCAdapter             - Deleted 0 old message(s).
2009-04-17 11:59:59,601 [ce Adaptor Task] DEBUG
JDBCPersistenceAdapter         - Cleanup done.
2009-04-17 11:59:59,601 [ce Adaptor Task] DEBUG
JournalPersistenceAdapter      - Checkpoint done.
2009-04-17 12:05:29,600 [ce Adaptor Task] DEBUG
JournalPersistenceAdapter      - Checkpoint started.
2009-04-17 12:05:29,600 [ce Adaptor Task] DEBUG
JDBCPersistenceAdapter         - Cleaning up old messages.
2009-04-17 12:05:29,601 [ce Adaptor Task] DEBUG
DefaultJDBCAdapter             - Executing SQL: DELETE FROM ACTIVEMQ_MSGS
WHERE ( EXPIRATION<>0 AND EXPIRATION<?) OR ID <= ( SELECT
min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM ACTIVEMQ_ACKS WHERE
ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)
2009-04-17 12:05:29,602 [ce Adaptor Task] DEBUG
DefaultJDBCAdapter             - Deleted 0 old message(s).
2009-04-17 12:05:29,602 [ce Adaptor Task] DEBUG
JDBCPersistenceAdapter         - Cleanup done.

That could be improved on I guess if it is a problem.

2009/4/15 Gary Tully <ga...@gmail.com>

> one thought, is this the default xml configuration? if so, is there a camel
> context with a camel route still in there?
>
> 2009/4/7 Rik Gruwez <ri...@admb.be>
>
>
>> I have setup a transactional message listener in Spring, using ActiveMQ
>> and
>> Atomikos for JTA. ActiveMQ uses MySQL for persistency, no journaling is
>> done. I noticed that the ID field in the activemq_msgs table increases for
>> no apparent reason, without messages being posted on the queues. I enabled
>> debug logging for ActiveMQ and noticed this:
>>
>> DEBUG [apache.activemq.TransactionContext] Start:
>> 172.16.203.64.tm0045200059172.16.203.64.tm455
>> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
>> DEBUG [apache.activemq.TransactionContext] End:
>> 172.16.203.64.tm0045200059172.16.203.64.tm455
>> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
>> DEBUG [apache.activemq.TransactionContext] Commit:
>> 172.16.203.64.tm0045200059172.16.203.64.tm455
>> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
>> DEBUG [apache.activemq.TransactionContext] Start:
>> 172.16.203.64.tm0045300059172.16.203.64.tm456
>> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
>> DEBUG [apache.activemq.TransactionContext] End:
>> 172.16.203.64.tm0045300059172.16.203.64.tm456
>> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
>> DEBUG [apache.activemq.TransactionContext] Commit:
>> 172.16.203.64.tm0045300059172.16.203.64.tm456
>> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
>> DEBUG [apache.activemq.TransactionContext] Start:
>> 172.16.203.64.tm0045400059172.16.203.64.tm457
>> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
>> DEBUG [apache.activemq.TransactionContext] End:
>> 172.16.203.64.tm0045400059172.16.203.64.tm457
>> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
>> DEBUG [apache.activemq.TransactionContext] Commit:
>> 172.16.203.64.tm0045400059172.16.203.64.tm457
>> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
>> DEBUG [apache.activemq.TransactionContext] Start:
>> 172.16.203.64.tm0045500059172.16.203.64.tm458
>> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
>> DEBUG [apache.activemq.TransactionContext] End:
>> 172.16.203.64.tm0045500059172.16.203.64.tm458
>> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
>> DEBUG [apache.activemq.TransactionContext] Commit:
>> 172.16.203.64.tm0045500059172.16.203.64.tm458
>> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>>
>> XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
>>
>> And this keeps going on. Any idea what is causing this?
>>
>> Regards,
>> Rik Gruwez
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Lots-of-XA-transactions-going-on-for-no-apparent-reason-tp22929377p22929377.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> http://blog.garytully.com
>
> Open Source SOA
> http://FUSESource.com
>



-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com

Re: Lots of XA transactions going on for no apparent reason

Posted by Gary Tully <ga...@gmail.com>.
one thought, is this the default xml configuration? if so, is there a camel
context with a camel route still in there?

2009/4/7 Rik Gruwez <ri...@admb.be>

>
> I have setup a transactional message listener in Spring, using ActiveMQ and
> Atomikos for JTA. ActiveMQ uses MySQL for persistency, no journaling is
> done. I noticed that the ID field in the activemq_msgs table increases for
> no apparent reason, without messages being posted on the queues. I enabled
> debug logging for ActiveMQ and noticed this:
>
> DEBUG [apache.activemq.TransactionContext] Start:
> 172.16.203.64.tm0045200059172.16.203.64.tm455
> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
> DEBUG [apache.activemq.TransactionContext] End:
> 172.16.203.64.tm0045200059172.16.203.64.tm455
> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
> DEBUG [apache.activemq.TransactionContext] Commit:
> 172.16.203.64.tm0045200059172.16.203.64.tm455
> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435323030303539:3137322e31362e3230332e36342e746d343535
> DEBUG [apache.activemq.TransactionContext] Start:
> 172.16.203.64.tm0045300059172.16.203.64.tm456
> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
> DEBUG [apache.activemq.TransactionContext] End:
> 172.16.203.64.tm0045300059172.16.203.64.tm456
> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
> DEBUG [apache.activemq.TransactionContext] Commit:
> 172.16.203.64.tm0045300059172.16.203.64.tm456
> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435333030303539:3137322e31362e3230332e36342e746d343536
> DEBUG [apache.activemq.TransactionContext] Start:
> 172.16.203.64.tm0045400059172.16.203.64.tm457
> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
> DEBUG [apache.activemq.TransactionContext] End:
> 172.16.203.64.tm0045400059172.16.203.64.tm457
> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
> DEBUG [apache.activemq.TransactionContext] Commit:
> 172.16.203.64.tm0045400059172.16.203.64.tm457
> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435343030303539:3137322e31362e3230332e36342e746d343537
> DEBUG [apache.activemq.TransactionContext] Start:
> 172.16.203.64.tm0045500059172.16.203.64.tm458
> DEBUG [apache.activemq.TransactionContext] Started XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
> DEBUG [apache.activemq.TransactionContext] End:
> 172.16.203.64.tm0045500059172.16.203.64.tm458
> DEBUG [apache.activemq.TransactionContext] Ended XA transaction:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
> DEBUG [apache.activemq.TransactionContext] Commit:
> 172.16.203.64.tm0045500059172.16.203.64.tm458
> DEBUG [activemq.transaction.XATransaction] XA Transaction commit:
>
> XID:1096044365:3137322e31362e3230332e36342e746d30303435353030303539:3137322e31362e3230332e36342e746d343538
>
> And this keeps going on. Any idea what is causing this?
>
> Regards,
> Rik Gruwez
>
> --
> View this message in context:
> http://www.nabble.com/Lots-of-XA-transactions-going-on-for-no-apparent-reason-tp22929377p22929377.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com