• Post Reply Bookmark Topic Watch Topic
  • New Topic

Help of XAException  RSS feed

 
Mike Sever
Ranch Hand
Posts: 56
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Who knows the reason of the blew exception? How to avoid it? Thanks in advance.
was version: 6.0
Implementation class name of "Oracle JDBC Driver" : oracle.jdbc.xa.client.OracleXADataSource

DSRA0304E: XAException occurred. XAException contents and details are: The cause is : null.
DSRA0302E: XAException occurred. Error code is: XAER_RMERR (-3). Exception is: <null>
WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@29bdd791. The error code was XAER_RMERR. The exception stack trace follows: javax.transaction.xa.XAException
at oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java(Compiled Code))
at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.recover(WSRdbXaResourceImpl.java(Compiled Code))
at com.ibm.ws.Transaction.JTA.XARminst.recover(XARminst.java(Compiled Code))
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java(Compiled Code))
at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java(Compiled Code))
at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java(Compiled Code))
at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2394)
at java.lang.Thread.run(Thread.java:570)
 
Vinay Raj
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The application server is trying to recover certain transactions that were in prepared state or heuristically complete. Typically these transactions were not committed/rollbacked when the application server crashed. So as a part of startup, the application server tries to recover these transactions. Unfortunately the transaction are no longer available as the datasource has taken a heuristic decision to commit/rollback.

The only way to fix this is to search for log files named trans*.log and delete them. This fix worked with WAS 4.0, let me know if it works with WAS 6
 
rock wang
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have the similar problem above mentioned with was 6.0, after remove the logs under tranlog directory of used profiles, it's running ok! Thanks for your suggestion.
 
Bujji Gadu
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was getting this error on my WAS6.1. Console keeps printing this error every minute or so. Error started after vpm disconnected in the middle of a transaction. Resolved after removing the logs from tranlog & parterlog directory. Thank you.
 
Rajah Nagur
Ranch Hand
Posts: 239
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bujji Gadu wrote:I was getting this error on my WAS6.1. Console keeps printing this error every minute or so. Error started after vpm disconnected in the middle of a transaction. Resolved after removing the logs from tranlog & parterlog directory. Thank you.


Thanks for the tip. It worked
 
bryan nelson
Ranch Hand
Posts: 95
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello there,

I too am getting this error on my WAS 6.1 console. Deleting the log files does indeed solve the problem, but only for a little while until they fill back up again.

Is there a more permanent solution to this problem?

Thanks!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!