Atomikos Forum

Problem with configuration of transaction timeout

As soon as a transaction takes more than 120 seconds I get the following log entries:

ActiveStateHandler: Timeout/setRollbackOnly of ACTIVE coordinator !

When the service logic is finished, the transaction is rolled back.

I have to increase the timeout but I was not able to find out where this timeout is configured. Personally I don't have configured a timeout of two minutes anywhere. Additionally, I was not able to find which code causes the rollback.

My questions:

How can I change the timeout configuration?

Which code causes the rollback?


More details:

In UserTransactionImp I set the transaction timout to 300 (five minutes) but this value does not affect the abovementioned timeout at all.

Setting a transaction-specific timeout via Spring's @Transactional annotation does not change the behaviour.

Setting com.atomikos.icatch.default_jta_timeout in transaction.properties does not affect the abovementioned timeout.

Hint: The abovementioned transaction does not use JMS but only the SQL database.

The stack:
- Atomikos 3.8.0 (same behaviour with 3.9.3)
- Hibernate 3.5.4-Final
- MySQL 5.x
- JMS 1.1
- ActiveMQ 5.7
- Spring 3.2.1.RELEASE

Thanks in advance for any help.
Rod Witzel Send private email
Tuesday, March 11, 2014
 
 
Hard to say without looking into your configuration details, which takes some time. Would you have a budget for support?
Guy Pardon Send private email
Friday, June 06, 2014
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics