Atomikos Forum

Hi Guy,

Back in September I have posted the stated issue and below is the content of my post:

I am getting the following exception when trying to retrieve data from the db.

Stacktrace:

SEVERE: Servlet.service() for servlet default threw exception
com.atomikos.datasource.ResourceException: resume for XID com.atomikos.spring.jdbc.tm0000300017com.atomikos.spring.jdbc.tm2 raised -5: invalid arguments were given for the XA operation
    at com.atomikos.datasource.xa.XAResourceTransaction.resume(Unknown Source)

Can anyone tell me what does this error mean?

Some more info:
Database : SQL Server
JDBC Driver : jtds-1.2.2
TransactionEssentials : 3.3.4
Hibernate : 3.2
Spring: 2.5.3

I still very much wanted to use Atomikos with my application so I did another lookup the web and came across the 'KnownProblems' of Atomikos with Hibernate 3.2.6 GA. Atomikos says the issue should be resolved in TransactionsEssentials 3.4.

I gave it another try by replacing version 3.3 with 3.4 hoping my issue will be resolve, but to my dissappointment the problem still persists but with a different error this time around. Below is a portion of the error produced by tm.out:

08-10-31 15:30:17,843 [main] Starting read of logfile C:\apps\eclipse_3.3.2\.\tmlog116.log
08-10-31 15:30:17,843 [main] Done read of logfile
08-10-31 15:30:17,952 [main] dataSource1: refreshed XAResource
08-10-31 15:30:17,999 [main] dataSource2: refreshed XAResource
08-10-31 15:30:30,477 [http-8080-Processor25] resume for XID 10.241.16.102.tm000030008710.241.16.102.tm3 raised -8: the supplied XID already exists in this XA resource
javax.transaction.xa.XAException: XAER_DUPID: The XID identifies an existing transaction.
    at net.sourceforge.jtds.jdbc.XASupport.raiseXAException(XASupport.java:677)
    at net.sourceforge.jtds.jdbc.XASupport.xa_start(XASupport.java:191)
    at net.sourceforge.jtds.jdbcx.JtdsXAResource.start(JtdsXAResource.java:105)
    at com.atomikos.datasource.xa.XAResourceTransaction.resume(XAResourceTransaction.java:610)
    at com.atomikos.datasource.xa.session.BranchEnlistedStateHandler.<init>(BranchEnlistedStateHandler.java:32)
    at com.atomikos.datasource.xa.session.NotInBranchStateHandler.checkEnlistBeforeUse(NotInBranchStateHandler.java:32)
    at com.atomikos.datasource.xa.session.TransactionContext.checkEnlistBeforeUse(TransactionContext.java:60)
    at com.atomikos.datasource.xa.session.SessionHandleState.notifyBeforeUse(SessionHandleState.java:151)
    at com.atomikos.jdbc.AtomikosConnectionProxy.enlist(AtomikosConnectionProxy.java:160)
    at com.atomikos.jdbc.AtomikosConnectionProxy.invoke(AtomikosConnectionProxy.java:100)


Could this be another bug or is it still my app's problem?

My guess is that you deleted the .epoch file and now you get duplicate transaction IDs because of that...

HTH

Do you mean by com.atomikos.spring.jdbc.tm.epoch and 10.241.16.102.tm.epoch? Any other .epoch file that are missing? I only have these 2.

10.241.16.102.tm.epoch is the one. If you delete it and restart then you may get these errors. Just make sure to keep it.