Error - BEA-110412 - WEblogic 8.1 sp4 +sql server 2005

Question

i using two connecion pooling
FIrst is - bea MS sql server 2000 TYpe 4XA version 7 2000
second is - bea MS sql server 2000 TYpe 4 version 7 2000
am getting this . ne one tell why this error happens ?
<May 3, 2007 10:44:49 AM IST> <Error> <JTA> <BEA-110412> <Name=[EJB
StatelessBean.findateFilter(java.lang
.String,java.util.Date,java.util.Date)],Xid=BEA1-0098FB74440133C475C1(740772),Status=Committed,Heuristi
cErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=120,
activeThread=Thread[ExecuteThread: '13' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue:
'weblogic.kernel.Default'],XAServerResourceInfo[XAPool]=(ServerResourceInfo[XAPool]=(
state=committed,assigned=AX),xar=XAPool,re-Registered = false),SCInfo[ade+AX]=
(state=committed),properties=({weblogic.transaction.name=[EJB
StatelessBean.findDateFilter(java.lang.Strin
g,java.util.Date,java.util.Date)]}),local properties=({}),OwnerTransactionManager=ServerTM[ServerCoordi
natorDescriptor=(CoordinatorURL=AccountEX+192.168.11.21:7001+Trade+t3+, XAResources={},NonXAResources={
})],CoordinatorURL=AX+192.168.11.21:7001+Tade+t3+) completed heuristically: (XAPool, H
euristicHazard, ()) >
<May 3, 2007 10:44:49 AM IST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transacti
on Name=[EJB findDateFilter(java.lang.String,java.util.Date,java.util.Date)],Xid=BEA1-0098FB
74440133C475C1(740772),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwed
Others=0,seconds since begin=0,seconds left=120,XAServerResourceInfo[XAPool]=(ServerResourceIn
fo[XAPool]=(state=committed,assigned=AX),xar=XAPool,re-Registered = false),SCI
nfo[Tade+AX]=(state=committed),properties=({weblogic.transaction.name=[EJB
StatelessBean.findDateFilter(java.lang.String,java.util.Date,java.util.Date)]}),
local properties=({}),OwnerTransactionManager=
ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AX+192.168.11.21:7001+Tade+t3+, XAResource
s={},NonXAResources={})],CoordinatorURL=AccountEX+192.168.11.21:7001+Tade+t3+): javax.transaction.Heur
isticMixedException: (XAPool, HeuristicHazard, ())
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.jav
a:296)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:246)
at weblogic.ejb20.internal.BaseEJBLocalObject.postInvoke(BaseEJBLocalObject.java:363)
at FacadeEJB_fnbmmb_ELOImpl.findDateFilter(BvTradexFacadeEJB_fnbmmb_ELOImpl.java:1375)
at AxAxInst.doSelect(AxAxInst.java:230)
at hub.hubmp.HUBMPTransportFinal.execute(HUBMPTransportFinal.java:81)
at jsp_servlet._hubmp.__batchurl._jspService(endrequest.jsp:8)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1
006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at hub.hubmp.servlet.FOPFilter.doFilter(FOPFilter.java:44)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at hub.hubmp.servlet.UtfFilter.doFilter(UtfFilter.java:36)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletCont
ext.java:6724)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
.>

Answer 1

this is an error when you somehow timeout the connection on DB without going through the WLS...
This can happen if the oracle setting are designed to timeout ideal connections or some one does it manually...
Also this can be found in case of Locks or some corrupt data on oracle which makes the JTA transaction end abnormally...