HeuristicMixedException

          We are using WebLogic 6.1 and Oracle 8.1.7 database on a Solaris Box. I have a
          client program accessing an EJB. This EJB is mapped to a VIEW in the database.
          Because of some restrictions we have to use a DBLINK for this view to access
          data residing on another database.
          When we test our client we get the following stack trace. The client program
          just reads the data.
          Any thought on this is highly appreciated. Thanks.
          Start server side stack trace:
          javax.transaction.HeuristicMixedException: (weblogic.jdbc.jts.Connection, Heuris
          ticHazard, (javax.transaction.xa.XAException: Io exception: Protocol violation))
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
          rverTransactionImpl.java:237)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
          sactionImpl.java:190)
          at weblogic.ejb20.internal.BaseEJBHome.postHomeInvoke(BaseEJBHome.java:3
          74)
          at weblogic.ejb20.internal.EntityEJBHome.finder(EntityEJBHome.java:466)
          at com.cingular.estore.catalog.CatalogRatePlanTextBean_nlgesf_HomeImpl.f
          indTextByStoreIdAndCategoryId(CatalogRatePlanTextBean_nlgesf_HomeImpl.java:85)
          at com.cingular.estore.catalog.CatalogRatePlanTextBean_nlgesf_HomeImpl_W
          LSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
          ef.java:93)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          

Hi! You have two options:
          1 - To simply make it go away, shut down all WLS servers,
          and delete any ".tlog" file. Note well, that if there are any
          real transactions that were prepared but not committed,
          they will be unavailable for the coming recover. If you
          have no ongoing transactions, this should be OK.
          2 - Otherwise you could boot our servers with the
          JTA/2PC debug logging flags, and then send the server
          log with the debug, and the tlog file(s) to bea support.
          Joe Weinstein

Similar Messages

  • Got javax.transaction.HeuristicMixedException  when calling EJB business methods

              I have developed two EJBs. One is a stateless session bean,
              called InventorySessionBean(JNDI name: Inventory); the other one
              is a CMP Entity Bean called InventoryBean(JNDI name:
              InventoryBean). The InventoryBean represents the business object
              of Inventory. InventoryBean is declared CMT and all methods in
              the beans have attribute "Required". The InventorySessionBean is a session facade
              which encapsulate the business methods of
              InventoryBean. InventorySessionBean is declared CMT and all
              methods in the bean have attribute"RequiresNew" The backend
              database is Ingres.
              I have setup JDBC connection pool, Datasource and Tx Datasource.
              There is a client program which invokes InventorySessionBean to get business data
              from database.
              Actually the InventorySessionBean invokes InventoryBean entity bean to get data
              from database.
              After I starting up the weblogic server, I ran the client program to get data,
              everything works fine.
              After a period of time (about 50 minutes ) from starting the WLS server, I reran
              the client program.
              I got following exceptions:
              Exception while commiting Tx : Name=[EJB com.memec.na.mppl.businessobjects.inventory.InventorySessionBean.getPriceAndAvailability(java.lang.String,ja
              va.lang.String,java.lang.String,java.lang.String)],Xid=4:916d7da2142a593c(2094524),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
              since begin=3,seconds left=119,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committed,assigned=leiWLS),SCInfo
              [leiwang+leiWLS]=(state=committed),properties=({weblogic.transaction.name=[EJBcom.memec.na.mppl.businessobjects.inventory.InventorySessionBean.getPriceAndAvailability(java.lang.String,java.lang.String,java.lang.String,java.lang.String)],
              weblogic.jdbc=t3://10.1.129.124:7001}),OwnerTransactionManage
              r=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=leiWLS+10.1.129.124:7001+leiwang+,
              Resources={})],CoordinatorURL=leiWLS+10.1.129.124:7001+leiwa
              ng+); nested exception is:
              javax.transaction.HeuristicMixedException: (weblogic.jdbc.jts.Connection,
              HeuristicHazard, (javax.transaction.xa.XAException: Error dequeueing
              message for statement connection # 23 type S))
              java.rmi.RemoteException: Exception while commiting Tx : Name=[EJB com.memec.na.mppl.businessobjects.inventory.InventorySessionBean.getPriceAndAvailab
              ility(java.lang.String,java.lang.String,java.lang.String,java.lang.String)],Xid=4:916d7da2142a593c(2094524),Status=Committed,HeuristicErrorCode=XA_HEU
              RHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=3,seconds left=119,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=committe
              d,assigned=leiWLS),SCInfo[leiwang+leiWLS]=(state=committed),properties=({weblogic.transaction.name=[EJB
              com.memec.na.mppl.businessobjects.inventory.In
              ventorySessionBean.getPriceAndAvailability(java.lang.String,java.lang.String,java.lang.String,java.lang.String)],
              weblogic.jdbc=t3://10.1.129.124:7001
              }),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=leiWLS+10.1.129.124:7001+leiwang+,
              Resources={})],CoordinatorURL=leiWL
              S+10.1.129.124:7001+leiwang+); nested exception is:
              javax.transaction.HeuristicMixedException: (weblogic.jdbc.jts.Connection,
              HeuristicHazard, (javax.transaction.xa.XAException: Error dequeueing
              message for statement connection # 23 type S))
              javax.transaction.HeuristicMixedException: (weblogic.jdbc.jts.Connection, HeuristicHazard,
              (javax.transaction.xa.XAException: Error dequeueing message
              for statement connection # 23 type S))
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
              at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
              at com.memec.na.mppl.businessobjects.inventory.InventorySessionBean_9wgxw_EOImpl.getPriceAndAvailability(InventorySessionBean_9wgxw_EOImpl.jav
              a:224)
              at com.memec.na.mppl.processors.Outbound3A2Processor.getData(Outbound3A2Processor.java:202)
              Stop the WLS server and restart it again. Everything works well.
              Any comments to this problem would be really appreciated. Thanks.
              

    Hi
    I was using the session bean.Your suggestion helped me a lot.Perfect.
    I debug my program and found that from ejbCreate()exception is getting.
    I was getting the datasource object thro ejb create() initialisation.
    Somehow the look up jndi which i mentioned was not interpretting from ejb-jar.xml ias-ejb-jar.xml and datasource ref .Due to this iam getting jndi Namenotfound exception which in turns to null pointer as datasource is getting null.
    when i hardcoded in the ejb the the jndi name for datasource it is working fine.Bit worried all the existing ejbs working with the xml referenced datasource and jndi,but when i added a new ejb with same properties it is failing to get the jndi name.
    Piece of code from ias-ejb-jar.xml
    <resource-ref>
              <res-ref-name>myDataSource</res-ref-name>
              <jndi-name>jdbc/nb/myData</jndi-name>
    </resource-ref>
    Piece of code from ejb-jar.xml
    <resource-ref>
              <res-ref-name>myDataSource</res-ref-name>
              <res-type>javax.sql.DataSource</res-type>
              <res-auth>Container</res-auth>
    </resource-ref>
    Thanks a lot meka

  • Weblogic Server HeuristicMixedException

    Hi
    I've been encountering the following exception occassionally. I'm using Weblogic server 8.1 SP5 and connecting to 9i Oracle DB. Appreciate any help to solve this.
    <Error> <JTA> <BEA-110412> <Name=[EJB com.liferay.portal.ejb.UserManagerEJB.getAllLayouts(java.lang.String)],Xid=BEA1-79D34965B736AAD3495F(17057455),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=81,seconds left=38,activeThread=Thread[ExecuteThread: '20' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[TX1]=(ServerResourceInfo[TX1]=(state=committed,assigned=mainServer),xar=TX1,re-Registered = false),SCInfo[AAPPS+mainServer]=(state=committed),properties=({weblogic.transaction.name=[EJB com.liferay.portal.ejb.UserManagerEJB.getAllLayouts(java.lang.String)]}),local properties=({weblogic.jdbc.jta.TX1=weblogic.jdbc.wrapper.TxInfo@1bc97fd}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=mainAdmin:8401+APPS+t3+, XAResources={TX1, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_jms1_81_NotDurable, JMS_NBSDummyJMSServer_NotDurable},NonXAResources={})],CoordinatorURL=mainAdmin:8401+APPS+t3+) completed heuristically: (TX1, HeuristicHazard, ()) >
    <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.liferay.portal.ejb.UserManagerEJB.getAllLayouts(java.lang.String)],Xid=BEA1-79D34965B736AAD3495F(17057455),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=81,seconds left=38,XAServerResourceInfo[TX1]=(ServerResourceInfo[TX1]=(state=committed,assigned=mainServer),xar=TX1,re-Registered = false),SCInfo[AAPPS+mainServer]=(state=committed),properties=({weblogic.transaction.name=[EJB com.liferay.portal.ejb.UserManagerEJB.getAllLayouts(java.lang.String)]}),local properties=({weblogic.jdbc.jta.TX1=weblogic.jdbc.wrapper.TxInfo@1bc97fd}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=mainAdmin:8401+APPS+t3+, XAResources={TX1, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_jms1_81_NotDurable, JMS_NBSDummyJMSServer_NotDurable},NonXAResources={})],CoordinatorURL=mainAdmin:8401+APPS+t3+): javax.transaction.HeuristicMixedException: (TX1, HeuristicHazard, ())
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:278)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:320)
    at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
    Cheers,
    bayisuper

    no, it support partially.
    I just want to encrypt my data (due to client requirement)
    and i found in documentation that it supports
    Encryption & Integrity
    http://download-west.oracle.com/docs/cd/A87860_01/doc/java.817/a83724/advanc2.htm#1022022
    Strange is, my whole J2EE-application works fine, but having problem only one EJB which reads/writes BLOB in Database ...
    Sanjay

  • Exceptions  - javax.transaction.HeuristicMixedException In Logs

    Using Oracle BPM 10.3 MP2 Enterprise Edition
    Version: 10.3.2
    Build: #100874.
    This exception is coming up in weblogic console logs.
    ####<Apr 29, 2011 8:14:52 AM CDT> <Error> <JTA> <fada1wap29> <BPM-CNM29> <BPM Directory Polling> <<anonymous>> <BEA1-1E6FEB3B248E3819C483> <> <1304082892584> <BEA-110412> <Xid=BEA1-1E6FEB3B248E3819C483(215626675),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=120,activeThread=Thread[BPM Directory Polling,5,Pooled Threads],XAServerResourceInfo[aqualogicCNM-JDBCDataSource]=(ServerResourceInfo[aqualogicCNM-JDBCDataSource]=(state=committed,assigned=BPM-CNM29),xar=aqualogicCNM-JDBCDataSource,re-Registered = false),SCInfo[bpmXprod+BPM-CNM29]=(state=committed),properties=({}),local properties=({weblogic.jdbc.jta.aqualogicCNM-JDBCDataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=BPM-CNM29+10.128.245.238:7001+bpmXprod+t3+, XAResources={WLStore_bpmXprod__WLS_BPM-CNM29, aqualogicCNM-JDBCDataSource, weblogic.jdbc.wrapper.JTSXAResourceImpl, engineCNM-JDBCDataSource},NonXAResources={})],CoordinatorURL=BPM-CNM29+10.128.245.238:7001+bpmXprod+t3+) completed heuristically: (aqualogicCNM-JDBCDataSource, HeuristicHazard, ()) >
    ####<Apr 29, 2011 8:14:52 AM CDT> <Info> <EJB> <fada1wap29> <BPM-CNM29> <BPM Directory Polling> <<anonymous>> <> <> <1304082892588> <BEA-010227> <EJB Exception occurred during invocation from home or business: fuego.ejbengine.ejb.engine_startup_enginecnm_mjkqiy_LocalHomeImpl@11241739 threw exception: fuego.server.exception.EngineRuntimeException: Server runtime exception. An error has occurred during the commit. Details : [Caused by 1 exceptions:
    javax.transaction.HeuristicMixedException: (aqualogicCNM-JDBCDataSource, HeuristicHazard, ())
        at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:302)
        at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
        at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:283)
        at weblogic.ejb.container.internal.usertransactioncheck.BaseUserTransactionProxy.commit(BaseUserTransactionProxy.java:28)
        at fuego.connector.impl.J2EETransactionCoordinator.commit(J2EETransactionCoordinator.java:55)
        at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:413)
        at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
        at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
        at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
        at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
        at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
        at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
        at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
        at fuego.ejbengine.ejb.EngineStartupBean.executeItem(EngineStartupBean.java:189)
        at fuego.ejbengine.ejb.EngineStartupBean.updateFromDirectory(EngineStartupBean.java:169)
        at fuego.ejbengine.ejb.engine_startup_enginecnm_mjkqiy_ELOImpl.updateFromDirectory(engine_startup_enginecnm_mjkqiy_ELOImpl.java:365)
        at fuego.ejbengine.servlet.DirectoryPollingServlet$DirectoryPollingTask.runImpl(DirectoryPollingServlet.java:43)
        at fuego.ejbengine.servlet.AbstractSchedulerServlet$ScheduledTask.run(AbstractSchedulerServlet.java:199)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
    And also
    weblogic.transaction.RollbackException: Could not prepare resource 'aqualogicCNM-JDBCDataSource
    [BEA][Oracle JDBC Driver]Oracle XA Error Occurred. Native Error: 24756
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:336)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:283)
    at weblogic.ejb.container.internal.usertransactioncheck.BaseUserTransactionProxy.commit(BaseUserTransactionProxy.java:28)
    at fuego.connector.impl.J2EETransactionCoordinator.commit(J2EETransactionCoordinator.java:55)
    at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:413)
    at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
    at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
    at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
    at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
    at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
    at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:79)
    at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
    at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
    at fuego.server.AbstractSecureEngineImpl.getBookmarks(AbstractSecureEngineImpl.java:75)
    at fuego.ejbengine.EJBSecureEngineAdapter.getBookmarks(EJBSecureEngineAdapter.java:98)
    at fuego.ejbengine.engine_enginecnm_ljzdng_EOImpl.getBookmarks(engine_enginecnm_ljzdng_EOImpl.java:1176)
    at fuego.ejbengine.engine_enginecnm_ljzdng_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(ActivatableServerRef.java:85)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: javax.transaction.xa.XAException: [BEA][Oracle JDBC Driver]Oracle XA Error Occurred. Native Error: 24756
    at weblogic.jdbcx.oracle.OracleImplXAResource.checkError(Unknown Source)
    at weblogic.jdbcx.oracle.OracleImplXAResource.prepare(Unknown Source)
    at weblogic.jdbcx.base.BaseXAResource.prepare(Unknown Source)
    at weblogic.jdbc.jta.DataSource.prepare(DataSource.java:867)
    at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1277)
    at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:500)
    at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:380)
    at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2581)
    at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2228)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:270)
    ... 25 more
    <Apr 29, 2011 8:28:11 AM CDT> <Warning> <JTA> <BEA-110486> <Transaction BEA1-4C1D5A1A76393819C483 cannot complete commit processing because resource [weblogic.jdbc.wrapper.JTSXAResourceImpl] is unavailable. The transaction will be abandoned after 78,152 seconds unless all resources acknowledge the commit decision.>
    Any one faced similar issue

    Hi Tim,
    I remember that one from writing a 2pc tx manager ... I don't know when it
    happens in WL but it usually occurs in a tx manager when a series of
    resources are being committed successfully and then one fails (although it
    was already prepared for commit) so the manager has to figure out
    "heuristically" what to do with the remaining prepared resources -- should
    it commit or roll back -- and then it has to report that some were both
    (i.e. "mixed").
    Are you using 2pc ... multiple resources ... etc.?
    Peace,
    Cameron Purdy
    Tangosol Inc.
    << Tangosol Server: How Weblogic applications are customized >>
    << Download now from http://www.tangosol.com/download.jsp >>
    "Tim Ozor" <[email protected]> wrote in message
    news:3c079160$[email protected]..
    We are seeing the following exception very sporadically with WL6.1. I am
    curious as to whether anybody could provide any useful information that
    would aid in our debug.
    Thanks.
    Tim Ozor ([email protected])
    javax.transaction.HeuristicMixedException
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:237)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:190)
    at
    weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
    at
    weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(UnknownSource)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace

  • HeuristicMixedException on VMS with 6.1sp2

    Has anyone using VMS encountered the random unexplained
    javax.transaction.HeuristicMixedException with 6.1sp2 that was
    suppose to have been fixed in 6.1sp3.
    http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html#1147388
    "064232,The javax.transaction.HeuristicMixedException is no
    longer being thrown sporadically at commit."
    I ask because there is not currently a 6.1ps3 release for VMS, we are looking
    to port from Sun, and we had this HeuristicMixedException regularly on Sun.

    Hi Paul,
    this is how I got Cocoon 2.0.4 running on WLS 6.1.4
    (Download the Cocoon source from http://xml.apache.org/cocoon/dist/)
    Remove all but the following JARs from lib/optional
    commons-jxpath-1.0.jar
    jing-20020724.jar
    resolver-20020130.jar
    servlet_2_2.jar
    commons-logging-1.0.jar
    jtidy-04aug2000r7-dev.jar
    rhino-1.5r3.jar
    xt-19991105.jar
    Update lib/jars.xml to reflect these changes
    build clean
    build webapp -Dinclude.webapp.libs=yes
    Copy the following JARs to a suitable lib-directory:
    xercesImpl-2.0.0.jar
    xml-apis.jar
    xalan-2.3.1.jar
    xt-19991105.jar:
    java/lib/tools.jar
    Deploy the resluting cocoon.war and you should have a Cocoon up and running that
    can do the XML->HTML Hello World sample. The status page works fine too.
    If you need a more competent Cocoon, try adding the required JARs on the class
    path (or add them the to your webapp-build if you are confident that WLS are capable
    of handling their manifests).
    Good luck
    /Peter
    "Paul Lee" <[email protected]> wrote:
    >
    Hi all, forgive me if this is not the right "Install" forum, but I am
    looking for
    some pointers/success stories in running Cocoon 2 with WLS 6.1 SP2 (Solaris
    preferably).
    I have followed the official installation instructions from Cocoon and
    searched
    the weblogic newsgroups, but none of them worked. Perhaps none of them
    were specifically
    about 6.1sp2.
    If anyone has any advice or pointers it would be greatly appreciated.
    Thanks,
    Paul

  • Re:  javax.transaction.HeuristicMixedException

    Hi,
    While i am running my ejb application I got below Exception, Can any one please help
    ERROR ZoneInitialMessageBean - Error committing transaction:: javax.transaction.HeuristicMixedException: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: Connection has been administratively destroyed. Reconnect.))
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:298)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
    at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:436)
    at weblogic.ejb.container.internal.BaseLocalObject.postInvokeTxRetry(BaseLocalObject.java:286)
    at com.timeamerica.nettimej.ejb.session.updates.ZoneUpdatesSession_w5locg_ELOImpl.generateInitialUserUpdateMsgs(ZoneUpdatesSession_w5locg_ELOImpl.java:262)
    at com.timeamerica.nettimej.mdb.clocks.ZoneInitialMessageBean.onMessage(ZoneInitialMessageBean.java:122)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:429)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    ; nested exception is: javax.transaction.HeuristicMixedException: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: Connection has been administratively destroyed. Reconnect.))
    Thanks in Advance
    Bhaskar
    Edited by: 920422 on May 25, 2012 6:04 AM

    Hi
    I have code the delay-updates-until-end-of-tx as False in the ZonesBean. After building that, I have transferd into remote server through SSH, I got the below Exception. Is there any other solution with respect to Heuristic Exception. Can any one help please...
    Thanks in Advance
    Bhaskar.
    weblogic.j2ee.validation.ComplianceException: In the RDBMS CMP bean 'Zones', the <delay-updates-until-end-of-tx> tag is set to 'false'. This conflicts with the default setting 'true' for tag <enable-batch-operations> and tag <order-database-operations>. Either set <delay-updates-until-end-of-tx> to 'true', or set the other two tags to 'false'.
    at weblogic.ejb.container.cmp.rdbms.compliance.RDBMSBeanChecker.checkDelayDatabaseInsertUntilConflictDelayUpdatesUntilEndOfTx(RDBMSBeanChecker.java:1002)
    at weblogic.ejb.container.cmp.rdbms.compliance.RDBMSBeanChecker.checkBean(RDBMSBeanChecker.java:202)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.ejb.container.cmp.rdbms.compliance.RDBMSBeanChecker.runComplianceCheck(RDBMSBeanChecker.java:114)
    at weblogic.ejb.container.cmp.rdbms.compliance.RDBMSComplianceChecker.checkCompliance(RDBMSComplianceChecker.java:109)
    at weblogic.ejb.container.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:387)
    at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:505)
    at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:454)
    at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:117)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1182)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
    at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:558)
    at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:454)
    at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:117)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1182)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
    Truncated. see log file for complete stacktrace

  • Weblogic throwing javax.transaction.HeuristicMixedException

    Hi,
    Our application uses MQJMS binding and weblogic transaction manager to receive and send messages to and from external queue. We got "javax.transaction.HeuristicMixedException" when we restarted our application at some point of time. All the messages except two were successfully processed. These messages were stuck in database for processing, but were pushed to the MQ queue. Later on, the same messages got processed again. No other error/exception is logged
    except below stack trace :
    WSATGatewayRM_AdminServer_LUCM_TXN},NonXAResources={})],CoordinatorURL=AdminServer+10.237.252.77:27025+LUCM_TXN+t3+): javax.transaction.HeuristicMixedException: (BANCS_EAI_TXN_DataSource_LUCM_TXN, HeuristicHazard, ())
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:305)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
    at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:257)
    at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:121)
    at weblogic.ejb.container.internal.NewJMSMessagePoller.timerExpired(NewJMSMessagePoller.java:204)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    The above error looks very generic. How come the messages were sent to the Queue but not committed in the DB. Can someone help on this ?

    This exception is thrown to report that a heuristic decision was made and that some relevant updates have been committed and others have been rolled back.
    The reason for the rollback can be that some RuntimeException was thrown in processing the messages.
    Have you also looked in the logging of the database or your MQ provider, maybe it was unable to give a commit to the weblogic transactionmanager, which
    is controlling the XA transaction.

  • Javax.transaction.HeuristicMixedException

              This seems to be a common problem (system throws HeuristicMixedException) when an
              EJB (Session Bean) from one WLS is trying to communicate to a second EJB (SessionBean)
              which deployed on another WLS.
              From the past articles, I saw people suggested that the two WL Servers should have
              the same system password. Is this the solution for this problem? Does anyone know
              the causes of this confusing exception?
              Thanks,
              Steven
              

              I am getting the same error...in my case the System passwords are the same. How do
              we resolve this???
              Thanks
              "Steve Cheung" <[email protected]> wrote:
              >
              >This seems to be a common problem (system throws HeuristicMixedException)
              >when an
              >EJB (Session Bean) from one WLS is trying to communicate to a second EJB
              >(SessionBean)
              >which deployed on another WLS.
              >
              >From the past articles, I saw people suggested that the two WL Servers should
              >have
              >the same system password. Is this the solution for this problem? Does anyone
              >know
              >the causes of this confusing exception?
              >
              >Thanks,
              >Steven
              

  • HeuristicMixedException with usertransactions

    Hi,
    I'm testing distributed EJB configuration with two Weblogic 6.1's in different
    computers, A and B. A has some simple test JSP's which call the EJB's on B. B
    is Windows 2000 with the EJB's and data source to Oracle 9.2, drivers oci920_8.
    When I attempt to use UserTransactions in the JSP page as in:
         Context ctx = getRemoteContext();
         UserTransaction tx = (UserTransaction) ctx.lookup
              ("javax.transaction.UserTransaction");
         tx.begin();
    // ..... get the EJB and call several methods ....
         tx.commit();
    I get the exception:
    Stacktrace = javax.transaction.HeuristicMixedException at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:247)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:240)
    at jsp_servlet._distributed_ejb.__recordList._jspService(__recordList.java:257)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    When I do not use UserTransactions and let each EJB method call be in it's own,
    container-initiated transaction the code works OK, but that's not what I want
    to test.
    getRemoteContext() is normal (?):
    static Context getRemoteContext() throws Exception {
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    h.put(Context.PROVIDER_URL, SERVER_B_URL);
    h.put(Context.SECURITY_PRINCIPAL, USER);
    h.put(Context.SECURITY_CREDENTIALS, PASS);
    return new InitialContext(h);

    Hi,
    We've had similar problems with WL 6.x when calling different non clustered
    WL ejb servers.
    I know for sure that two-phase commit was broken at some pint in WL6 (might
    have been fixed in a patch or service pack).
    Also, you need to use distinct domain names when you connect from one server
    to another. I remember using the same domain name was triggering the same
    exception you are seeing (we're using WL7 now).
    Alex.
    "Janne" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi,
    I'm testing distributed EJB configuration with two Weblogic 6.1's indifferent
    computers, A and B. A has some simple test JSP's which call the EJB's onB. B
    is Windows 2000 with the EJB's and data source to Oracle 9.2, driversoci920_8.
    When I attempt to use UserTransactions in the JSP page as in:
    Context ctx = getRemoteContext();
    UserTransaction tx = (UserTransaction) ctx.lookup
    ("javax.transaction.UserTransaction");
    tx.begin();
    // ..... get the EJB and call several methods ....
    tx.commit();
    I get the exception:
    Stacktrace = javax.transaction.HeuristicMixedException atweblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:237)
    atweblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:190)
    atweblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
    erImpl.java:247)
    atweblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManag
    erImpl.java:240)
    atjsp_servlet._distributed_ejb.__recordList._jspService(__recordList.java:257)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :265)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :304)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :200)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:2495)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2204)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    >
    When I do not use UserTransactions and let each EJB method call be in it'sown,
    container-initiated transaction the code works OK, but that's not what Iwant
    to test.
    getRemoteContext() is normal (?):
    static Context getRemoteContext() throws Exception {
    Properties h = new Properties();
    h.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    h.put(Context.PROVIDER_URL, SERVER_B_URL);
    h.put(Context.SECURITY_PRINCIPAL, USER);
    h.put(Context.SECURITY_CREDENTIALS, PASS);
    return new InitialContext(h);

  • Small error while opening web app

    When i open my web app which was deployed in Prod mode,
    i get the following error when i open the link in the browser
    *(305) Internal Error - A fatal exception occurred. javax.transaction.HeuristicMixedException: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: Io exception: Software caused connection abort: socket write error))*
    null
    But the same application is working fine in QA Server.
    The env is weblogic 8.1.3 and windows. There is only one domain in the prod server and that domain has only 1 admin server and 1 application has been deployed to it. The application was working fine before, but from last week, i am getting the error specified above.
    Thanks in Advance

    Hi,
    Check the below thread...
    Web Application Designer Opening Error

  • Phantom Context lookup or Is "java:" some kind of keyword ? ? ?

    I'm attempting to implement my own Context for capturing performance information out of a third party applications. I've run into a strange problem where the method call doesn't aways work even though the signature appears to be correct, with the only diffence being is the contents of the String that is passed in as a parameter. If the string starts with "java:" the method is not called. In the example below only "lookup [my-ruleHome]" is printed, I'd have expected "lookup [java:comp/UserTransaction]" to be printed as well.
    package com.blah;
    import javax.naming.*;
    import java.util.Hashtable;
    public class MyContext implements Context {
        Context realProviderCtx = null; 
        public MyContext (Hashtable env) throws NamingException {
          env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
          realProviderCtx = new InitialContext(env);
        public Object lookup(String name) throws NamingException {
           System.out.println("lookup [" + name + "]");
           return realProviderCtx.lookup(name);
    package com.blah;
    import java.io.*;
    // Packages for Servlets
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.util.Collection;
    import java.util.Iterator;
    import java.util.Properties;
    import java.util.Vector;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.ejb.FinderException;
    import javax.naming.NamingException;
    import java.rmi.RemoteException;
    import javax.rmi.PortableRemoteObject;
    import javax.transaction.UserTransaction;
    import javax.ejb.CreateException;
    import javax.ejb.RemoveException;
    public class SomeServlet extends HttpServlet {
      public void init(ServletConfig config) throws ServletException {
        super.init(config);
      * Method to process HTTP GET requests.
      public void doGet(HttpServletRequest p_req, HttpServletResponse p_res)
                                            throws ServletException, IOException {
         Collection rules = getRules();
         //  Do something here to display a webpage
      public Collection getRules() {
        Collection rules = null;
        Properties env = new Properties();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "blah.MyInitialContextFactory");
        env.put(Context.PROVIDER_URL, "t3://app-dev-01.blah.com:7003");                                                                           
        try
          Context cntx = new InitialContext(env);
          UserTransaction ut = (UserTransaction) cntx.lookup( "java:comp/UserTransaction" );
          ut.begin();
          RuleHome ruleHome = (RuleHome) cntx.lookup("my-ruleHome");
          rules = ruleHome.findAll();
          ut.commit();
        catch (NamingException ne)
           System.out.println("NamingException " + ne.toString());
           ne.printStackTrace();
        catch (FinderException fe)
           System.out.println("FinderException " + fe.toString());
        catch (java.rmi.RemoteException re) {
           System.out.println("RemoteException " + re.toString());
        } catch (javax.transaction.NotSupportedException nse) {
           System.out.println("NotSupportedException " + nse.toString());
        } catch (javax.transaction.RollbackException re) {
           System.out.println("RollbackException " + re.toString());
        } catch (javax.transaction.SystemException se) {
           System.out.println("SystemException " + se.toString());
        } catch (javax.transaction.HeuristicMixedException hme) {
           System.out.println("HeuristicMixedException " + hme.toString());
        } catch (javax.transaction.HeuristicRollbackException hre) {
           System.out.println("HeuristicRollbackException " + hre.toString());
        return rules;
    }

    I think I figured out my own issue. InitialContext is actually wrappering my context. Based on the documentation in http://java.sun.com/j2se/1.4.1/docs/api/javax/naming/InitialContext.html anything before the ":" is the scheme InitialContext's lookup method will use a different context provider based on the scheme and that's why my method was not being executed. Apparently the context provider for the scheme "java" was receiving the method call.

  • HeuristicHazard within a transaction using only one DataSource

    We have an ejb 2.0 application running under WL 7.0 SP1. Its CMP beans are
              persisted in two Oracle 9i databases, some beans from different databases
              are related (have CMR). We are using XA Oracle JDriver for both pools.
              The javax.transaction.HeuristicMixedException exception occurred when the
              client application called getId() method on the local interface of one of
              the beans. The client is a webapp deployed together with the ejbs in the one
              EAR.
              The mentioned bean doesn't have any CMR with any bean from the other
              database, and its transaction attribute is 'Required'. Therefore method call
              which resulted in HeuristicMixedException was using only one DataSource. Why
              did exception happened?
              

    No.
    There is a very slight increase in performance if you have two chips of the same size, but it is something that will only really show up in benchmarks.
    Get 1GB now and leave the other 256MB chip in there. When you have an extra $80 around doing nothing, grab another stick.

  • Exception after switching to Oracle 10g

    I have a working application running on weblogic server 9.1. The server has
    a DataSource pointing to an Oracle 9i instance (i am using the Oracle Thin
    XA driver).
    Now I tried to connect to an identical database schema running in Oracle 10g
    (with the same driver). Now weblogic throws errors while deploying the
    application:
    The problem seems to be with an cmp entity bean for the table G_ZM_FAB which
    is a synonym to a view in another schema. I have no problem accessing
    G_ZM_FAB with any database tool or with sqlplus. Only weblogic gives
    errors. Another entity bean pointing to a similar table works perfectly
    (the second entity bean has bean managed persistence).
    Do you have any idea where the problem might be? I have tried other drivers
    with no success (they give other errors). When I make G_ZM_FAB a normal
    table with the same structure and content, everyting works fine.
    Here is the server log with the exception that is thrown:
    === SNIP ===
    JAVA Memory arguments: -Xmx1536m -Xgc:parallel -d64
    WLS Start Mode=Production
    CLASSPATH=:/opt/bea/patch_weblogic910/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit150/lib/tools.jar:/opt/bea/weblogic91/server/lib/weblogic_sp.jar:/opt/bea/weblogic91/server/lib/weblogic.jar:/opt/bea/weblogic91/server/lib/webservices.jar::/opt/bea/weblogic91/common/eval/pointbase/lib/pbclient51.jar:/opt/bea/weblogic91/server/lib/xqrl.jar::/opt/bea/weblogic91/integration/lib/util.jar:
    PATH=/opt/bea/weblogic91/server/bin:/opt/bea/jrockit150/jre/bin:/opt/bea/jrockit150/bin:/opt/bea/user_projects/domains/Systemtest8010/bin:/opt/bea/user_projects/domains/Systemtest8010/runtime/bin:/opt/bea/user_projects/domains/Systemtest8010:/opt/ora10g/bin:/opt/bea/weblogic91/common/bin:/opt/bea/weblogic91/server/bin:/opt/sfw/bin:/usr/local/bin:/usr/bin::/usr/openwin/bin:/usr/local/kde/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.5.0_08"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
    BEA JRockit(R) (build
    R27.1.0-109-73164-1.5.0_08-20061129-1427-solaris-sparcv9, compiled mode)
    Starting WLS with line:
    /opt/bea/jrockit150/bin/java -jrockit -Xmx1536m -Xgc:parallel -d64 -Dpython.cachedir=/opt/bea/user_projects/domains/Systemtest8010/wlstTemp -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dpegasus.serverTyp=test -Dpegasus.application.description="Systemtestumgebung
    1" -da -Dplatform.home=/opt/bea/weblogic91 -Dwls.home=/opt/bea/weblogic91/server -Dwli.home=/opt/bea/weblogic91/integration -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/opt/bea/patch_weblogic910/profiles/default/sysext_manifest_classpath -Dweblogic.management.username=weblogic -Dweblogic.management.password=xxxxxxxx -Dweblogic.Name=Pegasus -Djava.security.policy=/opt/bea/weblogic91/server/lib/weblogic.policy
    weblogic.Server
    <28.08.2007 8.33 Uhr CEST> <Info> <WebLogicServer> <BEA-000377> <Starting
    WebLogic Server with BEA JRockit(R) Version
    R27.1.0-109-73164-1.5.0_08-20061129-1427-solaris-sparcv9 from BEA Systems,
    Inc.>
    <28.08.2007 8.33 Uhr CEST> <Info> <Management> <BEA-141107> <Version:
    WebLogic Server 9.1 Mon Dec 12 19:26:33 EST 2005 689178 >
    <28.08.2007 8.33 Uhr CEST> <Info> <WebLogicServer> <BEA-000215> <Loaded
    License : /opt/bea/license.bea>
    <28.08.2007 8.33 Uhr CEST> <Notice> <WebLogicServer> <BEA-000365> <Server
    state changed to STARTING>
    <28.08.2007 8.33 Uhr CEST> <Info> <WorkManager> <BEA-002900> <Initializing
    self-tuning thread pool>
    <28.08.2007 8.33 Uhr CEST> <Notice> <Log Management> <BEA-170019> <The
    server log
    file /pegasus_test/Systemtest8010/servers/Pegasus/logs/Pegasus.log is
    opened. All server side log events will be written to this file.>
    <28.08.2007 8.34 Uhr CEST> <Notice> <Security> <BEA-090082> <Security
    initializing using security realm myrealm.>
    <28.08.2007 8.34 Uhr CEST> <Notice> <WebLogicServer> <BEA-000365> <Server
    state changed to STANDBY>
    <28.08.2007 8.34 Uhr CEST> <Notice> <WebLogicServer> <BEA-000365> <Server
    state changed to STARTING>
    <28.08.2007 9.14 Uhr CEST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM
    DUAL" set up for pool "pegasus" failed with
    exception: "javax.transaction.xa.XAException".>
    <28.08.2007 9.14 Uhr CEST> <Error> <JTA> <BEA-110412>
    <Xid=BEA1-015D84121B5A4CC38D9
    (35424095),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=41,seconds left=82,activeThread=Thread[[ACTIVE]
    ExecuteThread: '0' for queue: 'weblogic.kernel.Default
    (self-tuning)',5,Pooled
    Threads],XAServerResourceInfo[pegasus]=(ServerResourceInfo[pegasus]=(state=committed,assigned=Pegasus),xar=pegasus,re-Registered
    =
    false),SCInfo[Systemtest8010+Pegasus]=(state=committed),properties=({}),local
    properties=({weblogic.jdbc.jta.pegasus=[ No XAConnection is attached to
    this
    TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=Pegasus+10.32.193.47:8010+Systemtest8010+t3+,
    XAResources={WLStore_Systemtest8010_FileStore-0,
    pegasus2},NonXAResources={})],CoordinatorURL=Pegasus+10.32.193.47:8010+Systemtest8010+t3+)
    completed heuristically: (pegasus, HeuristicHazard, ()) >
    <28.08.2007 9.14 Uhr CEST> <Error> <Deployer> <BEA-149231> <Unable to set
    the activation state to true for the application 'Pegasus-Application'.
    weblogic.application.ModuleException: Exception activating module:
    EJBModule(deploy/DEBTMR-G-EJB.jar)
    Unable to deploy EJB: G_ZM_FAB from deploy/DEBTMR-G-EJB.jar:
    [EJB:011007]Unable to create EJB Persistence Manager.
    javax.transaction.HeuristicMixedException: (pegasus, HeuristicHazard, ())
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:297)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
    at
    weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:271)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:298)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
    at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:170)
    at
    weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
    at
    weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
    at
    weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1292)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
    at
    weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
    at
    weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at
    weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:176)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:347)
    at
    weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
    at
    weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at
    weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at
    weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at
    weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:422)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
    Truncated. see log file for complete stacktrace
    [EJB:011007]Unable to create EJB Persistence Manager.
    javax.transaction.HeuristicMixedException: (pegasus, HeuristicHazard, ())
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:297)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
    at
    weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:271)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:298)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
    at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:170)
    at
    weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
    at
    weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
    at
    weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1292)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
    at
    weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
    at
    weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at
    weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:176)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:347)
    at
    weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
    at
    weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at
    weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at
    weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at
    weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    NestedException Message is :(pegasus, HeuristicHazard, ())
    at
    weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:311)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
    at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:170)
    at
    weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
    at
    weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
    Truncated. see log file for complete stacktrace
    === SNIP ===
    Greetings,
    Christian

    Christian Schmolzi wrote:
    I have a working application running on weblogic server 9.1. The server has
    a DataSource pointing to an Oracle 9i instance (i am using the Oracle Thin
    XA driver).
    Now I tried to connect to an identical database schema running in Oracle 10g
    (with the same driver). Now weblogic throws errors while deploying the
    application:
    The problem seems to be with an cmp entity bean for the table G_ZM_FAB which
    is a synonym to a view in another schema. I have no problem accessing
    G_ZM_FAB with any database tool or with sqlplus. Only weblogic gives
    errors. Another entity bean pointing to a similar table works perfectly
    (the second entity bean has bean managed persistence).
    Do you have any idea where the problem might be? I have tried other drivers
    with no success (they give other errors). When I make G_ZM_FAB a normal
    table with the same structure and content, everyting works fine.Odd. Well, we can assume that the issue is a difference in the
    JDBC-access behavior of the two DBMS versions. I would start by
    updating the ojdbc14.jar in your WLS's server\lib directory. Download
    and try Oracle's latest driver, and let me know if that solves it.
    Joe
    >
    Here is the server log with the exception that is thrown:
    === SNIP ===
    JAVA Memory arguments: -Xmx1536m -Xgc:parallel -d64
    WLS Start Mode=Production
    CLASSPATH=:/opt/bea/patch_weblogic910/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit150/lib/tools.jar:/opt/bea/weblogic91/server/lib/weblogic_sp.jar:/opt/bea/weblogic91/server/lib/weblogic.jar:/opt/bea/weblogic91/server/lib/webservices.jar::/opt/bea/weblogic91/common/eval/pointbase/lib/pbclient51.jar:/opt/bea/weblogic91/server/lib/xqrl.jar::/opt/bea/weblogic91/integration/lib/util.jar:
    PATH=/opt/bea/weblogic91/server/bin:/opt/bea/jrockit150/jre/bin:/opt/bea/jrockit150/bin:/opt/bea/user_projects/domains/Systemtest8010/bin:/opt/bea/user_projects/domains/Systemtest8010/runtime/bin:/opt/bea/user_projects/domains/Systemtest8010:/opt/ora10g/bin:/opt/bea/weblogic91/common/bin:/opt/bea/weblogic91/server/bin:/opt/sfw/bin:/usr/local/bin:/usr/bin::/usr/openwin/bin:/usr/local/kde/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.5.0_08"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
    BEA JRockit(R) (build
    R27.1.0-109-73164-1.5.0_08-20061129-1427-solaris-sparcv9, compiled mode)
    Starting WLS with line:
    /opt/bea/jrockit150/bin/java -jrockit -Xmx1536m -Xgc:parallel -d64 -Dpython.cachedir=/opt/bea/user_projects/domains/Systemtest8010/wlstTemp -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dpegasus.serverTyp=test -Dpegasus.application.description="Systemtestumgebung
    1" -da -Dplatform.home=/opt/bea/weblogic91 -Dwls.home=/opt/bea/weblogic91/server -Dwli.home=/opt/bea/weblogic91/integration -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/opt/bea/patch_weblogic910/profiles/default/sysext_manifest_classpath -Dweblogic.management.username=weblogic -Dweblogic.management.password=xxxxxxxx -Dweblogic.Name=Pegasus -Djava.security.policy=/opt/bea/weblogic91/server/lib/weblogic.policy
    weblogic.Server
    <28.08.2007 8.33 Uhr CEST> <Info> <WebLogicServer> <BEA-000377> <Starting
    WebLogic Server with BEA JRockit(R) Version
    R27.1.0-109-73164-1.5.0_08-20061129-1427-solaris-sparcv9 from BEA Systems,
    Inc.>
    <28.08.2007 8.33 Uhr CEST> <Info> <Management> <BEA-141107> <Version:
    WebLogic Server 9.1 Mon Dec 12 19:26:33 EST 2005 689178 >
    <28.08.2007 8.33 Uhr CEST> <Info> <WebLogicServer> <BEA-000215> <Loaded
    License : /opt/bea/license.bea>
    <28.08.2007 8.33 Uhr CEST> <Notice> <WebLogicServer> <BEA-000365> <Server
    state changed to STARTING>
    <28.08.2007 8.33 Uhr CEST> <Info> <WorkManager> <BEA-002900> <Initializing
    self-tuning thread pool>
    <28.08.2007 8.33 Uhr CEST> <Notice> <Log Management> <BEA-170019> <The
    server log
    file /pegasus_test/Systemtest8010/servers/Pegasus/logs/Pegasus.log is
    opened. All server side log events will be written to this file.>
    <28.08.2007 8.34 Uhr CEST> <Notice> <Security> <BEA-090082> <Security
    initializing using security realm myrealm.>
    <28.08.2007 8.34 Uhr CEST> <Notice> <WebLogicServer> <BEA-000365> <Server
    state changed to STANDBY>
    <28.08.2007 8.34 Uhr CEST> <Notice> <WebLogicServer> <BEA-000365> <Server
    state changed to STARTING>
    <28.08.2007 9.14 Uhr CEST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM
    DUAL" set up for pool "pegasus" failed with
    exception: "javax.transaction.xa.XAException".>
    <28.08.2007 9.14 Uhr CEST> <Error> <JTA> <BEA-110412>
    <Xid=BEA1-015D84121B5A4CC38D9
    (35424095),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=41,seconds left=82,activeThread=Thread[[ACTIVE]
    ExecuteThread: '0' for queue: 'weblogic.kernel.Default
    (self-tuning)',5,Pooled
    Threads],XAServerResourceInfo[pegasus]=(ServerResourceInfo[pegasus]=(state=committed,assigned=Pegasus),xar=pegasus,re-Registered
    =
    false),SCInfo[Systemtest8010+Pegasus]=(state=committed),properties=({}),local
    properties=({weblogic.jdbc.jta.pegasus=[ No XAConnection is attached to
    this
    TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=Pegasus+10.32.193.47:8010+Systemtest8010+t3+,
    XAResources={WLStore_Systemtest8010_FileStore-0,
    pegasus2},NonXAResources={})],CoordinatorURL=Pegasus+10.32.193.47:8010+Systemtest8010+t3+)
    completed heuristically: (pegasus, HeuristicHazard, ()) >
    <28.08.2007 9.14 Uhr CEST> <Error> <Deployer> <BEA-149231> <Unable to set
    the activation state to true for the application 'Pegasus-Application'.
    weblogic.application.ModuleException: Exception activating module:
    EJBModule(deploy/DEBTMR-G-EJB.jar)
    Unable to deploy EJB: G_ZM_FAB from deploy/DEBTMR-G-EJB.jar:
    [EJB:011007]Unable to create EJB Persistence Manager.
    javax.transaction.HeuristicMixedException: (pegasus, HeuristicHazard, ())
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:297)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
    at
    weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:271)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:298)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
    at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:170)
    at
    weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
    at
    weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
    at
    weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1292)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
    at
    weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
    at
    weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at
    weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:176)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:347)
    at
    weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
    at
    weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at
    weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at
    weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at
    weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:422)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
    Truncated. see log file for complete stacktrace
    [EJB:011007]Unable to create EJB Persistence Manager.
    javax.transaction.HeuristicMixedException: (pegasus, HeuristicHazard, ())
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:297)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
    at
    weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:271)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:298)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
    at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:170)
    at
    weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
    at
    weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
    at
    weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1292)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
    at
    weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at
    weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
    at
    weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at
    weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:176)
    at
    weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:347)
    at
    weblogic.management.deploy.internal.DeploymentAdapter$1.activate(DeploymentAdapter.java:50)
    at
    weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:232)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:168)
    at
    weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at
    weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at
    weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at
    weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    NestedException Message is :(pegasus, HeuristicHazard, ())
    at
    weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:311)
    at
    weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
    at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:170)
    at
    weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
    at
    weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
    Truncated. see log file for complete stacktrace
    === SNIP ===
    Greetings,
    Christian

  • Suitable EJB for operations on two tables

    Hi All,
    I would like to create a stateless session bean that removes a record from one table and inserts into another table. The method I will be using must be transactional integrity giving me "all or nothing proposition". How can I make sure the failure of the second database operation automatically results in the rollback of the first one.
    Thank you.

    Greetings,
    Hi All,
    I would like to create a stateless session bean that
    removes a record from one table and inserts into
    another table. The method I will be using must be
    transactional integrity giving me "all or nothing
    proposition". How can I make sure the failure of the
    second database operation automatically results in the
    rollback of the first one.The distributed transaction management of EJBs will take of this for you on the database side of things. What remains is that you code your bean appropriately for the transaction management model (BMT or CMT) of your bean...
    First, remember that a Stateless SB cannot carry transaction contexts across multiple client->bean method calls, so your resource operations must occur within the same client method call:
    * CMT *
    ...updateTables()
        try {
            /* Perform database operations... */
        catch( SQLException sqle ) {
            try {
                context.setRollbackOnly();  // Tell Trans. Mgr. operation failed
            catch( IllegalStateException ise ) {
                throw new EJBException( "Deployment error!" );
    }* BMT *
    ...updateTables()
    UserTransaction ut = null;
    try {
    ut = context.getUserTransaction();
    catch( IllegalStateException ise ) {
    throw new EJBException( "Deployment error!" );
    try {
    ut.begin();
    /* Perform database operations... */
    ut.commit();
    catch( SQLException sqle ) {
    try {
    ut.rollback();
    catch( IllegalStateException ise ) {
    throw new EJBException( "Deployment error!" );
    catch( <Exception+> e ) { ... }
    The last <Exception+> in the above code can be one of:
    * NotSupportedException - a consequence of calling ut.begin() and a transaction is already in effect
    * RollbackException - if the transaction cannot be commited (another participant called a ROLLBACK)
    * IllegalStateException - if a transaction is not in effect when ut.commit() is called
    Note: All transaction method calls may also throw a SystemException in case of (um, well...), system errors.
    In EJB 2.0 you can also get a HeuristicMixedException from ut.commit() if the trans. mgr. decided a ROLLBACK was necessary.
    I hope this helps.
    Thank you.Regards,
    Tony "Vee Schade" Cook

  • Integration Builder unexpected error

    When I'm using Configuration and Design Integration Builder for time to time I get such strange error message. Any idea what is going on?
    Unexpected error during message processing: javax.transaction.HeuristicMixedException: com.sap.engine.services.ts.exceptions.BaseHeuristicMixedException: One or more XAResources were not commited because of Exception in the second commit phase.
    at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:432)
    at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.commit(TransactionManagerImpl.java:316)
    at com.sap.engine.services.ts.jta.impl.UserTransaction.commit(UserTransaction.java:79)
    at com.sap.aii.ib.server.notification.AbstractMessageReceiver.commitMsgProcessingTx(AbstractMessageReceiver.java:223)
    at com.sap.aii.ib.server.notification.AbstractMessageReceiver.onMessage(AbstractMessageReceiver.java:138)
    at com.sap.jms.client.session.Session.run(Session.java:715)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: javax.transaction.xa.XAException: XA operation cannot be completed successfully.
    at com.sap.jms.client.xa.XAResource.commit(XAResource.java:47)
    at com.sap.engine.services.jmsconnector.spi.ManagedSession$XAManagedResource.commit(ManagedSession.java:322)
    at com.sap.engine.services.ts.jta.impl.ResourceList.commitTwoPhase(ResourceList.java:107)
    at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:360)
    ... 9 more

    Hi
    Check this thread
    error in ID
    Sameer

Maybe you are looking for

  • Creative Cloud App Screen Download error

    I continue to get the exclamation point in a triangle and it asks me to uninstall and then download it again. Needless to say I've don't his about five times and I keep getting the same error. PLEASE HELP!!

  • Scrolling Ebay listing pages has become jerky instead of smooth. With safari it's smooth.

    I see in the comments of others they are having the same problem: When you scroll an Ebay listing page there is a continuing jerky stop and start. It used to be smooth. I know it's Firefox because the problem doesn't exist when I use Safari as my bro

  • Old Toad? -- Rebuild iPhoto Library and lose NOTHING!

    Hi, Any help will be very much appreciated (I'm particularly hoping the old toad will be hopping over to this thread)... I'm running iPhoto 6 and have been using iPhoto since version 3.0. I have a library of about 10,000 photos which I have meticulou

  • Already Purchased content disappearing

    Albums that I have Purchased and already played on my both Itunes and Ipod after syncing are disappearing from my library. Itunes store says they are purchased but giving me no option to re-download the content or buy it again. What do I do in this s

  • JTAPI  jar file

    Hi I want to use JTAPI technology but i am unable to find out its jar file. if anyone knows about it then please tell me soon. You can also email me at [email protected] Thanx in advance. Best Regards. Asif