Eclipse Community Forums: Eclipse Process Manager (Stardust) » HeuristicMixedException on WebLogic during transaction commit

Home » Archived » Eclipse Process Manager (Stardust) » HeuristicMixedException on WebLogic during transaction commit(Weblogic transaction commit exception)

HeuristicMixedException on WebLogic during transaction commit [message #742653]

Thu, 20 October 2011 13:46

Eclipse User

HeuristicMixedException on WebLogic during transaction commit
A problem that has occured in several occasions:

2009-12-11 15:07:14,190 saId=26726 [STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'
WARN AuditTrailLogger:85 - Execution for event.daemon daemon failed.: Error committing transaction::
javax.transaction.HeuristicMixedException: (AuditTrail, HeuristicHazard, ())

This has been reported from WebLogic environments a couple of times and it happens when the WebLogic transaction that Stardust
uses is supposed to be committed.

Re: HeuristicMixedException on WebLogic during transaction commit [message #742655 is a reply to message #742653]

Thu, 20 October 2011 13:47

Eclipse User

It has to do with WebLogic's JTA transaction timeout settings being greater than the timeouts for the XA data source (AuditTrail DB). This leads to the database transaction timing out before the WebLogic transaction.

A general rule to follow is to make sure that WebLogic Server JTA timeout (either global, specific to an EJB or for individual transactions) is set to a lower value than the shortest timeout value configured/set for a participating XA resource (e.g., XA Transaction Timeout for Oracle XA JDBC connections). Not doing so can lead to an unexpected and inconsistent distributed transaction outcome, i.e., a participating XA Resource timing out before WebLogic Server JTA as the distributed transaction coordinator. The timed out XA Resource may take action to resolve its own part of the distributed transaction before WebLogic Server can take action. This will lead to heuristic error messages at the time when the WebLogic transaction manager tries to prepare/commit the distributed transaction.

The solution was that for the JDBC Connection Pools to set the XASetTransactionTimeout to true and XATransactionTimeout to zero ("When this parameter is set to zero, the XAResource Session Timeout will be set to the global transaction timeout.")

[Updated on: Thu, 20 October 2011 13:48] by Moderator

Re: HeuristicMixedException on WebLogic during transaction commit [message #742657 is a reply to message #742655]

Thu, 20 October 2011 13:49

Eclipse User

In addition to the application server's default transaction timeout settings the timeout in the server-specific deployment descriptor should be checked as well, e.g. weblogic-ejb-jar.xml.

The standard deployment descriptor shipped with Stardust contains the setting

 ...
<trans-timeout-seconds>600</trans-timeout-seconds>
...

This can be removed or adapted accordingly in order to not conflict with the other mentioned settings.

[Updated on: Fri, 21 October 2011 00:36] by Moderator

Re: HeuristicMixedException on WebLogic during transaction commit [message #742658 is a reply to message #742657]

Thu, 20 October 2011 13:49

Eclipse User

Setting the transaction timeouts correctly solved the problem.

Previous Topic:	Identify which button click initiated 'complete' method call of backing bean
Next Topic:	Stardust/JMS using ActiveMQ - Disable Prefetch Cache

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 22:59:13 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter