• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4552
  • Last Modified:

javax.transaction.SystemException: Heuristic hazard

Hi,All

My application is currently running on Weblogic7.01,HP-UX and Oracle9i.

I got the following error:

####<Nov 22, 2004 2:18:44 PM GMT+08:00> <Error> <EJB> <db> <myserver> <ExecuteThread: '4' for queue: 'default'>
 <kernel identity> <> <010025> <Exception during rollback of transaction 368:8f1c3b477f28edb9: javax.transaction.SystemException: Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAEx
ception: Io exception: Broken pipe))
        at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:345)
        at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:311)
        at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:258)
        at cn.com.ebis.e5s.admin.ejb.UserMgrEJB_ers64w_EOImpl.verifyLogin(UserMgrEJB_ers64w_EOImpl.java:704)
        at cn.com.ebis.e5s.admin.ejb.UserMgrEJB_ers64w_EOImpl_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
        at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)


Could anybody help me for this problem?

Thinks in Advance.
0
cocreate
Asked:
cocreate
  • 2
  • 2
1 Solution
 
kiranhkCommented:
According to BEA's documentation, the jDriver is deprecated (no longer supported) in WLS 7 SP5. Not sure when they stopped supporting it, but sometime after SP2,apparently.

if you are using TwoPhaseCommitEnabled="true" in the TXDataSource definition then change it and try again.
0
 
cocreateAuthor Commented:
thanks for your answer,but I need to useTwoPhaseCommitEnabled="true" in the TxDataSource definition.

what do I need to do?
0
 
rama_krishna580Commented:
Hi,

if you want to use this option ---> EnableTwoPhaseCommit=true

Admin Console field label: Emulate Two-Phase Commit for non-XA Driver
Default: false

When set to true, this attribute allows non-XA JDBC drivers to emulate participation in distributed transactions using JTA.

Use this option if the JDBC connection is the only participant in the transaction and there is no XA compliant JDBC driver available. With more than one resource participating in a transaction where one of them (the JDBC driver) is emulating an XA resource, you may see heuristic failures.

If this TxDataSource is associated with an XA connection pool, or if there is only one resource participating in the distributed transaction, then this setting is ignored.

Syntax:

<JDBCTxDataSource  DeploymentOrder="number"  
EnableTwoPhaseCommit=( "true" | "false" )  
JNDIName="String"  
Name="String"  
Notes="String"  
PoolName="String"  
RowPrefetchEnabled=( "true" | "false" )  
RowPrefetchSize="number"  
StreamChunkSize="number of bytes"  
Targets="list of Target names"/>

i hope this may help you...
best of luck...

R.K
0
 
rama_krishna580Commented:
For more info refer this documentation...
http://e-docs.bea.com/wls/docs81/config_xml/JDBCTxDataSource.html

R.K
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now