Atomikos Forum

In our application we using to XA Resources, JMS (ActiveMQ) and a DB (Postgres). When processing a high amount of message we that our JMS queue are faster then the database commites. So it can happen that the JMS message arrives on the queue before the database is up to date. Looking in the transaction logs we see that the JMS messages are committed before the database messages.

Is there any way to specify the order of commits in Atomikos? So we can change the order in first the database commit and next the JMS commit.

If you set com.atomikos.icatch.threaded_2pc=false in jta.properties then commits are done in the order of resource access. If you access the DB first, then it will be committed first.

HTH

What are the implications of setting com.atomikos.icatch.threaded_2pc=false?

In our case the start point is JMS, message is first taken from the before the database is requested. So setting 2pc=false has no effect is there any other way to switch the order of a commit? Does the order of declarations in the configurations has any impact?

Hi,

If the problem is on a _receiving_ queue then you should look for a solution on the sender side. In no way can the commit order change the order in which you receive messages. That is against the semantics of JMS/XA...

Best