ServerResourceInfo.isAccessibleAtAndAssignableTo

          I am running weblogic 7.0 SP2 on AIX.
          I have an EJB with required transactions that do selects, inserts and updates
          to Oracle databases and selects to DB2 databases.
          My server recently started spitting out the following exceptions. I got about
          5000 exceptions in 45 minutes.
          I found something about this exception being fixed in 6.1 SP5. Did the fix somehow
          get overlooked for weblogic 7.0? The case number was: CR092301.
          Any help would be appreciated.
          ####<Jun 2, 2003 10:15:13 AM CDT> <Warning> <rmi> <kp790055.test.kohls.com> <cuAS01>
          <ExecuteThread: '7' for queue: 'default'> <kernel identity> <> <080003> <RuntimeException
          thrown by rmi server: weblogic.transaction.internal.CoordinatorImpl.startCommit(Ljavax.transaction.xa.Xid;Ljava.lang.String;[Ljava.lang.String;ZZLweblogic.security.acl.internal.AuthenticatedUser;)
          java.lang.NullPointerException>
          java.lang.NullPointerException
          at weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignableTo(ServerResourceInfo.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerSCInfo.handleResource(ServerSCInfo.java(Inlined
          Compiled Code))
          at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java(Compiled
          Code))
          at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
          Source)(Compiled Code)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java(Compiled
          Code))
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compiled
          Code))
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(Compiled
          Code))
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          

          See CR107866 - there appears to be a patch for this issue.
          .Peter
          "Tania Rhinehart" <[email protected]> wrote:
          >
          >I am running weblogic 7.0 SP2 on AIX.
          >I have an EJB with required transactions that do selects, inserts and
          >updates
          >to Oracle databases and selects to DB2 databases.
          >
          >My server recently started spitting out the following exceptions. I
          >got about
          >5000 exceptions in 45 minutes.
          >
          >I found something about this exception being fixed in 6.1 SP5. Did the
          >fix somehow
          >get overlooked for weblogic 7.0? The case number was: CR092301.
          >
          >Any help would be appreciated.
          >
          >####<Jun 2, 2003 10:15:13 AM CDT> <Warning> <rmi> <kp790055.test.kohls.com>
          ><cuAS01>
          ><ExecuteThread: '7' for queue: 'default'> <kernel identity> <> <080003>
          ><RuntimeException
          >thrown by rmi server: weblogic.transaction.internal.CoordinatorImpl.startCommit(Ljavax.transaction.xa.Xid;Ljava.lang.String;[Ljava.lang.String;ZZLweblogic.security.acl.internal.AuthenticatedUser;)
          > java.lang.NullPointerException>
          >java.lang.NullPointerException
          > at weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignableTo(ServerResourceInfo.java(Compiled
          >Code))
          > at weblogic.transaction.internal.ServerSCInfo.handleResource(ServerSCInfo.java(Inlined
          >Compiled Code))
          > at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
          >Code))
          > at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java(Compiled
          >Code))
          > at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java(Compiled
          >Code))
          > at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
          >Source)(Compiled Code)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
          >Code))
          > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java(Compiled
          >Code))
          > at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java(Compiled
          >Code))
          > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compiled
          >Code))
          > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(Compiled
          >Code))
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled
          >Code))
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          

Similar Messages

  • Nullpointer in 'weblogic.transaction.internal.CoordinatorImpl

              I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
              My server has a transacted EJB which accesses Oracle and DB2 databases. I have
              been running my application for several months.
              Suddenly, yesterday it starting spitting out these exceptions a few times a minute.
              I cannot find the configuration change I made that would have caused this to
              suddenly start appearing. My code has not changed in 2 weeks.
              Has anyone seen this error before? Does anyone know what causes this, so that
              I can narrow my search?
              Thanks for your help,
              Tania
              ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025> <cuAS01> <ExecuteThread:
              '5' for queue: 'default'> <system> <> <000000> <RuntimeException thrown by rmi
              server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid: '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:qdomain4:cuAS01',
              oid: '261', implementation: 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
              java.lang.NullPointerException
              at weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignableTo(ServerResourceInfo.java(Compiled
              Code))
              at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(ServerTransactionImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorImpl.java(Compiled
              Code))
              at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
              Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
              Code))
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compiled
              Code))
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(Compiled
              Code))
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

              Thanks,
              The problem did clear up when the Unix server had to get bounced. I believe it
              was bounced for an unrelated issue.
              The one thing I noticed was that there were a couple of copies of my EJBs in the
              wlnotdelete directory that the server had been previously compliaining about.
              They went away after the Unix server was restarted and the NullPointer problem
              went away.
              We plan to upgrade to 7.1 soon, but will try to move to SP5 if we need to sooner.
              Thanks for your help.
              Tania Rhinehart
              Rajesh Mirchandani <[email protected]> wrote:
              >This is fixed in SP5. Open a case with [email protected] and reference
              >CR092301.
              >
              >Slava Imeshev wrote:
              >
              >> Hi Tania,
              >>
              >> I think you need to contact BEA support at [email protected]
              >>
              >> Regards,
              >>
              >> Slava Imeshev
              >>
              >> "Tania Rhinehart" <[email protected]> wrote in message
              >> news:[email protected]...
              >> >
              >> > I am using Weblogic 6.1 SP4 on JDK 1.3.1 on AIX.
              >> > My server has a transacted EJB which accesses Oracle and DB2 databases.
              > I
              >> have
              >> > been running my application for several months.
              >> > Suddenly, yesterday it starting spitting out these exceptions a few
              >times
              >> a minute.
              >> > I cannot find the configuration change I made that would have caused
              >this
              >> to
              >> > suddenly start appearing. My code has not changed in 2 weeks.
              >> >
              >> > Has anyone seen this error before? Does anyone know what causes
              >this, so
              >> that
              >> > I can narrow my search?
              >> >
              >> > Thanks for your help,
              >> > Tania
              >> >
              >> > ####<Mar 4, 2003 12:35:48 PM CST> <Warning> <Dispatcher> <ksp12025>
              >> <cuAS01> <ExecuteThread:
              >> > '5' for queue: 'default'> <system> <> <000000> <RuntimeException
              >thrown by
              >> rmi
              >> > server: 'weblogic.rmi.internal.BasicServerRef@105 - jvmid:
              >> '-4285102758410085945S:10.1.21.21:[18120,18120,18121,18121,18120,18121,-1]:q
              >> domain4:cuAS01',
              >> > oid: '261', implementation:
              >> 'weblogic.transaction.internal.CoordinatorImpl@311671da''>
              >> >
              >> > java.lang.NullPointerException
              >> > at
              >> weblogic.transaction.internal.ServerResourceInfo.isAccessibleAtAndAssignable
              >> To(ServerResourceInfo.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
              >> rverTransactionImpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.ServerTransactionImpl.assignResourcesToSelf(Se
              >> rverTransactionImpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
              >> ctionImpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.SubCoordinatorImpl.startCommit(SubCoordinatorI
              >> mpl.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
              >> > Source)
              >> > at
              >> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java(Compiled
              >> > Code))
              >> > at
              >> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java(Compi
              >> led
              >> > Code))
              >> > at
              >> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java(C
              >> ompiled
              >> > Code))
              >> > at
              >> weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
              >> > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >> >
              >
              >--
              >Rajesh Mirchandani
              >Developer Relations Engineer
              >BEA Support
              >
              >
              

  • Error while comitting a transaction in oSB. The following is the error stack

    Error while comitting a transaction in OSB. The following is the error stack
    <Apr 20, 2015 12:00:15 AM MDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-1AE41F1CAE45F2B146FD(296700848),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=2,seconds left=120,XAServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(ServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(ServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(state=rolledback,assigned=OSB_MS1),xar=WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_11603460297,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.jta.DataSource]=(ServerResourceInfo[weblogic.jdbc.jta.DataSource]=(state=ended,assigned=none),xar=CMSDS,re-Registered = false),SCInfo[OSB_PRDKS_DOMAIN+OSB_MS1]=(state=rolledback),SCInfo[SOA_PRDKS_DOMAIN+SOA_MS2]=(state=pre-prepared),properties=({}),local properties=({weblogic.jdbc.jta.CMSDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=OSB_MS1+soaprd-vip-osb-ms1.cos.is.keysight.com:8001+OSB_PRDKS_DOMAIN+t3+, XAResources={eis/wls/Queue, WEDB_EVEREST_OSB_PRDKS_DOMAIN, XREFDS_OSB_PRDKS_DOMAIN, eis/activemq/Queue, CustomSchemaDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS1_OSB_PRDKS_DOMAIN, eis/tibjmsDirect/Queue, eis/jbossmq/Queue, eis/Apps/Apps, MobileApps_AOS_MDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_DRDS_OSB_PRDKS_DOMAIN, WSATGatewayRM_OSB_MS1_OSB_PRDKS_DOMAIN, eis/webspheremq/Queue, eis/AQ/aqSample, SBLPROD_OSB_PRDKS_DOMAIN, wlsbjmsrpDataSource_OSB_PRDKS_DOMAIN, eis/aqjms/Queue, CMSDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_WseeFileStore_auto_1, FAP_OSB_PRDKS_DOMAIN, eis/sunmq/Queue, eis/pramati/Queue, FMWAPPDS_OSB_PRDKS_DOMAIN, weblogic.jdbc.jta.DataSource, GSDC_OSB_PRDKS_DOMAIN, eis/tibjms/Topic, eis/fioranomq/Topic, WLStore_OSB_PRDKS_DOMAIN_FileStore_MS1, PresidioOracleAppsDS_OSB_PRDKS_DOMAIN, GSDCDS_OSB_PRDKS_DOMAIN, eis/aqjms/Topic, CustOutDS_OSB_PRDKS_DOMAIN, OFMW/Logging/BAM, MobileAppsDS_OSB_PRDKS_DOMAIN, FIDDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN__WLS_OSB_MS1, HRMSDS_OSB_PRDKS_DOMAIN, WEDB_OSB_PRDKS_DOMAIN, OracleAppsDS_OSB_PRDKS_DOMAIN, eis/wls/Topic, eis/tibjms/Queue, eis/tibjmsDirect/Topic, IntrastatDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_COSDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS2_OSB_PRDKS_DOMAIN, EVEREST_WEDB_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1, Everest_OSB_PRDKS_DOMAIN},NonXAResources={})],CoordinatorURL=SOA_MS2+soaprd-vip-soa-ms2.cos.is.keysight.com:8002+SOA_PRDKS_DOMAIN+t3+): javax.transaction.SystemException: Lost connection to server while commit was in progress, ignoring because initiating server is not coordinating server. Remote Exception received=weblogic.rjvm.PeerGoneException: ; nested exception is:
            java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
            java.io.InvalidClassException: oracle.jdbc.xa.OracleXAException; local class incompatible: stream classdesc serialVersionUID = -2542408691177300269, local class serialVersionUID = -4551795881821760665
            at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:376)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:552)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:423)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:325)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

    Hi,
    Have you tried Cancelling the release before adding the version?
    Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
    Please let me know if it worked!
    Vijay

  • Error while calling ejb service call from BPM service

    Hi,
    We are using the Oracle 11.1.1.5.0
    We are calling ejb service call from BPM service to update the data to Oracle database.
    We are getting the below error when we executing the ejb service call from BPM Service.
    <Error> <EJB> <BEA-010026> <Exception occurred du
    ring commit of transaction Name=[EJB oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliver
    yBean.handleCallback(java.lang.String,java.lang.String,java.lang.String,int,bool
    ean)],Xid=BEA1-45B91984D57960994897(30845116),Status=Rolled back. [Reason=javax.
    transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a p
    articipant in two-phase commit. To force this participation, set the GlobalTrans
    actionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhas
    eCommit for the Data Source = EBSConnection],numRepliesOwedMe=0,numRepliesOwedOt
    hers=0,seconds since begin=1,seconds left=60,XAServerResourceInfo[SOADataSource_
    base_domain]=(ServerResourceInfo[SOADataSource_base_domain]=(state=rolledback,as
    signed=soa_server1),xar=SOADataSource,re-Registered = false),XAServerResourceInf
    o[ArCnTaskForms@EBSConnection@EBSConnection_base_domain]=(ServerResourceInfo[ArC
    nTaskForms@EBSConnection@EBSConnection_base_domain]=(state=rolledback,assigned=s
    oa_server1),xar=weblogic.jdbc.wrapper.JTSEmulateXAResourceImpl@fa5476,re-Registe
    red = false),SCInfo[base_domain+soa_server1]=(state=rolledback),properties=({web
    logic.jdbc.remote.EBSConnection=t3://192.168.10.114:8001, weblogic.transaction.n
    ame=[EJB oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean.handleCallback(java.la
    ng.String,java.lang.String,java.lang.String,int,boolean)]}),local properties=({w
    eblogic.jdbc.jta.SOADataSource=[ No XAConnection is attached to this TxInfo ]}),
    OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=soa
    server1+192.168.10.114:8001+basedomain+t3+, XAResources={eis/tibjms/Queue, eis
    /activemq/Queue, WLStore_base_domain_BPMJMSFileStore, WLStore_base_domain__WLS_s
    oa_server1, eis/fioranomq/Topic, eis/jbossmq/Queue, eis/Apps/Apps, eis/websphere
    mq/Queue, eis/AQ/aqSample, WLStore_base_domain_SOAJMSFileStore, eis/aqjms/Queue,
    WSATGatewayRM_soa_server1_base_domain, eis/sunmq/Queue, eis/pramati/Queue, SSCo
    nnectionDS_base_domain, eis/tibjms/Topic, eis/tibjmsDirect/Queue, eis/wls/Queue,
    eis/tibjmsDirect/Topic, EDNDataSource_base_domain, eis/wls/Topic, eis/aqjms/Top
    ic, RL3TST_base_domain, ArCnTaskForms@EBSConnection@EBSConnection_base_domain, S
    OADataSource_base_domain, WLStore_base_domain_UMSJMSFileStore_auto_2},NonXAResou
    rces={})],CoordinatorURL=soa_server1+192.168.10.114:8001+base_domain+t3+): weblo
    gic.transaction.RollbackException: Could not prepare resource 'ArCnTaskForms@EBS
    Connection@EBSConnection_base_domain
    JDBC driver does not support XA, hence cannot be a participant in two-phase comm
    it. To force this participation, set the GlobalTransactionsProtocol attribute to
    LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source
    = EBSConnection
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
    TransactionImpl.java:1881)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
    rverTransactionImpl.java:345)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
    sactionImpl.java:239)
    at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocal
    Object.java:622)
    at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetr
    y(BaseLocalObject.java:455)
    at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(Sess
    ionLocalMethodInvoker.java:52)
    at oracle.bpm.bpmn.engine.ejb.impl.BPMNDeliveryBean_of8dk6_ICubeDelivery
    LocalBeanImpl.handleCallback(Unknown Source)
    at com.collaxa.cube.engine.dispatch.message.instance.CallbackDeliveryMes
    sageHandler.handle(CallbackDeliveryMessageHandler.java:47)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(Dispatc
    hHelper.java:140)
    at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatc
    hTask.java:88)
    at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTas
    k.java:64)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
    utor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
    .java:908)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: javax.transaction.xa.XAException: JDBC driver does not support XA, he
    nce cannot be a participant in two-phase commit. To force this participation, se
    t the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended)
    or EmulateTwoPhaseCommit for the Data Source = EBSConnection
    at weblogic.jdbc.wrapper.JTSXAResourceImpl.prepare(JTSXAResourceImpl.jav
    a:83)
    at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
    sourceInfo.java:1327)
    at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
    sourceInfo.java:513)
    at weblogic.transaction.internal.ServerSCInfo$1.run(ServerSCInfo.java:36
    8)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
    gWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    .>
    <12 Oct, 2012 12:34:40 PM IST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-00
    0000> <failed to handle message
    javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot
    be a participant in two-phase commit. To force this participation, set the Globa
    lTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateT
    woPhaseCommit for the Data Source = EBSConnection
    at weblogic.jdbc.wrapper.JTSXAResourceImpl.prepare(JTSXAResourceImpl.jav
    a:83)
    at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
    sourceInfo.java:1327)
    at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerRe
    sourceInfo.java:513)
    at weblogic.transaction.internal.ServerSCInfo$1.run(ServerSCInfo.java:36
    8)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
    gWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    <12 Oct, 2012 12:34:40 PM IST> <Error> <oracle.soa.bpel.engine.dispatch> <BEA-00
    0000> <Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.
    message.instance.CallbackDeliveryMessage"; the reported exception is: Error comm
    itting transaction:; nested exception is: javax.transaction.xa.XAException: JDBC
    driver does not support XA, hence cannot be a participant in two-phase commit.
    To force this participation, set the GlobalTransactionsProtocol attribute to Log
    gingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = EB
    SConnection
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    ORABPEL-05002
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.
    message.instance.CallbackDeliveryMessage"; the reported exception is: Error comm
    itting transaction:; nested exception is: javax.transaction.xa.XAException: JDBC
    driver does not support XA, hence cannot be a participant in two-phase commit.
    To force this participation, set the GlobalTransactionsProtocol attribute to Log
    gingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = EB
    SConnection
    This error contained an exception thrown by the message handler.
    Check the exception trace in the log (with logging level set to debug mode).
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(Dispatc
    hHelper.java:207)
    at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatc
    hTask.java:88)
    at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTas
    k.java:64)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
    utor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
    .java:908)
    at java.lang.Thread.run(Thread.java:662)
    >
    Could any body help on this issue.It is little bit urgent for us to resolve.
    Thanks in advance.

    Thanks Sudipto Desmukh,
    The link is helpful me to resolve this issue.
    Thanks,
    Narasimha E

  • Can't get rid of a TX - message keeps appearing and being processed by OSB

    I have some sort of a poison message or TX I can't flush. Every 10 seconds I get a log message like the second one below, and the number of pending messages in multiple places and OSB proxy service messages processed keep climbing - all without producing any new messages on my part. I've tried deleting the default server store on the OSB managed server and the filestore for the JMS server. No luck.
    When this first started happening, the error messages looked like the first one below. Something I did caused the change, I assume. However, it's the same TX ID throughout.
    So, first, how can I get rid of this thing? It's driving me nuts and keeping me from closing out a POC.
    Second, why is it happening? I have one suspicion - could it be because that somehow we configured mutiple domains with the same name for a distributed application? It's not my normal practice but it happened. These domains don't communicate directly, but there are domains that need to communicate with both. So I'm guessing the name ambiguity may be hurting us. Just a guess, though.
    In this case, the sgosb domain's proxy service (this domain name is unique) is receiving messages from a queue resident in the pega_domain in Singapore and another proxy service is putting a message to another queue in the pega_domain in the UK. This is not in a single TX; the first proxy service forwards the message to a queue in the sgosb_domain, the second proxy service gets that message and puts it into the other pega_domain. It's an XA TX for each proxy service.
    Just to make it more fun, the sgosb_domain has another proxy service reading from a different queue and forwarding it to a queue in the third pega_domain in the US.
    TIA for any help or insight.
    Oh yes, the OSB domain is WLS 10.3.4, while the pega_domains are WLS 10.3.2
    Original error message
    ####<Apr 13, 2011 4:32:13 AM GMT> <Error> <EJB> <sg01app510> <sgosb_1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'>
    <<anonymous>> <> <92f54a30d60e6302:-4b6d523c:12f4cfeaabc:-8000-0000000000000123> <1302669133597> <BEA-010026> <Exception occurred during commit of
    transaction Xid=BEA1-039B0B6D3D0E77C1B135(1898471720),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
    begin=0,seconds left=600,XAServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=(ServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=
    (state=new,assigned=none),xar=null,re-Registered = false),SCInfo[sgosb_domain+sgosb_1]=(state=rolledback),SCInfo[pega_domain+pega_1]=(state=rolledback),properties=
    ({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+, XAResources={eis/tibjms/Topic,
    WLStore_sgosb_domain_FileStore_auto_1, eis/aqjms/Queue, eis/wls/Queue, eis/tibjms/Queue, WLStore_sgosb_domain__WLS_sgosb_1, eis/AQ/aqSample, eis/aqjms/Topic,
    eis/pramati/Queue, eis/sunmq/Queue, WLStore_sgosb_domain_WseeFileStore_auto_1, WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1,
    WSATGatewayRM_sgosb_1_sgosb_domain, eis/jbossmq/Queue, eis/activemq/Queue, eis/fioranomq/Topic, eis/tibjmsDirect/Topic, eis/wls/Topic,
    eis/tibjmsDirect/Queue, eis/Apps/Apps, eis/webspheremq/Queue},NonXAResources={})],CoordinatorURL=pega_1+nj09mhm5078:22111+pega_domain+t3+):
    javax.transaction.RollbackException: This transaction does not exist on the coordinating server.  It was probably rolled back and forgotten.
            at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
            at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
            at weblogic.transaction.internal.CoordinatorImpl_1032_WLStub.commit(Unknown Source)
            at weblogic.transaction.internal.TransactionImpl$1.run(TransactionImpl.java:331)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.transaction.internal.SecureAction.runAction(SecureAction.java:72)
            at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:327)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:252)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:326)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.RollbackException: This transaction does not exist on the coordinating server.  It was probably rolled back and forgotten.
            at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:94)
            at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
            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(SecurityManager.java:147)
            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)
    The error message I'm getting now
    ####<Apr 13, 2011 4:51:38 AM GMT> <Error> <EJB> <sg01app510> <sgosb_1> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <>
    <92f54a30d60e6302:-42808c28:12f4d3173cb:-8000-0000000000000032> <1302670298730> <BEA-010026> <Exception occurred during commit of transaction
    Xid=BEA1-0011D0679BA5074B8E12(1930603846),Status=Rolled back. [Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds
    left=60,XAServerResourceInfo[WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1]=(ServerResourceInfo[WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1]=
    (state=rolledback,assigned=sgosb_1),xar=WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1239571724,re-Registered =
    false),XAServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=(ServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=
    (state=rolledback,assigned=pega_1),xar=null,re-Registered = false),SCInfo[sgosb_domain+sgosb_1]=(state=rolledback),SCInfo[pega_domain+pega_1]=(state=rolledback),properties=
    ({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+, XAResources={eis/tibjms/Topic,
    WLStore_sgosb_domain_FileStore_auto_1, eis/aqjms/Queue, eis/wls/Queue, eis/tibjms/Queue, WLStore_sgosb_domain__WLS_sgosb_1, eis/AQ/aqSample, eis/aqjms/Topic, eis/pramati/Queue, eis/sunmq
    /Queue, WLStore_sgosb_domain_WseeFileStore_auto_1, WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1, WSATGatewayRM_sgosb_1_sgosb_domain, eis/jbossmq/Queue, eis/activemq
    /Queue, eis/fioranomq/Topic, eis/tibjmsDirect/Topic, eis/wls/Topic, eis/tibjmsDirect/Queue, eis/Apps/Apps, eis/webspheremq/Queue},NonXAResources=
    {})],CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+): weblogic.transaction.RollbackException: Unknown reason
            at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1881)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:345)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:326)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.xa.XAException
            at weblogic.store.gxa.internal.GXAResourceImpl.prepare(GXAResourceImpl.java:1227)
            at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1295)
            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:2593)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1321)
            at weblogic.transaction.internal.SubCoordinatorImpl.startPrepare(SubCoordinatorImpl.java:183)
            at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
            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(SecurityManager.java:147)
            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)
    .>Edited by: SteveElkind on Apr 13, 2011 5:50 AM

    Tom,
    Thanks! Succinct and easy to understand as ever.
    Yup, that covers it - I had also just seen this in the docs after looking at atheek1's earlier response (thanks to him/her as well). It's covered almost as clearly there as you state it here (http://download.oracle.com/docs/cd/E11035_01/wls100/jta/trxcon.html).
    While the ESB domains meet all of those requirements (except for cross-domain security configuration), each of the other two sets of domains (3 in each set) do not meet the naming uniqueness criteria for domain and server names; they do for JMS server names. I saw the store names in the TX identifier string as included resource, and assumed they might play a part - that's why I changed them. As you say, an unnecessary change. Oh well - it was an easy one.
    My normal practice has been for unique names in the past, due to problems I had years ago with cross-domain JMS traffic in an earlier WLS version. I guess it's the wrong time to have forgotten that lesson.
    Does anyone know of a quick way of changing a domain name quickly without rebuilding the domain? In the past WLST resulted in incomplete copies for me, is that still a problem? Server names are easy, just some global search-and-replace in the config.xml file (and in the management scripts, too)
    /Steve

  • Lock request timeout ...

    Dear Rob ,
    To consult you again and thanks in advise.
    The following code is my session bean's method ,
    public void updateDclrDiagnose(String hospitalNo,String dclrYYMM,int postSeq,String
    diagKindSign,String[] diagNoAll,String caseNo,String operatorNo) throws CommonException{
    DclrDiagnoseHome dclrDiagNoseHome = getDclrDiagnoseHome();
    Collection c = dclrDiagNoseHome.findByDiagKindSign (hospitalNo,dclrYYMM,postSeq,diagKindSign);
    Iterator it = c.iterator();
    while(it.hasNext()){
    DclrDiagnose dclrDiagnose = (DclrDiagnose) it.next();
    log("delete diagnose - diagNo=" + dclrDiagnose.getDcg_diag_no());
    dclrDiagnose.remove();
    for(int i = 0; i < diagNoAll.length; i++){
    log("create diagnose - diagNo=" + diagNoAll);
    dclrDiagNoseHome.create(hospitalNo,dclrYYMM,postSeq,diagKindSign,i+1,diagNoAll[i],caseNo,operatorNo);
    log("method complete!!");
    When my client JSP call this method several times later , then it will throw an exception
    , as following
    javax.transaction.TransactionRolledbackException: The lock request from EJB:com.
    syscom.prjnckm.hospitalization.declaration.entity.DclrDiagnose with primary key:
    com.syscom.prjnckm.hospitalization.declaration.entity.DclrDiagnosePK@74dfef60 ti
    med-out after waiting 0 ms. The transaction or thread requesting the lock was:Na
    me=[EJB com.syscom.prjnckm.hospitalization.declaration.session.DclrMaintainBean.
    updateDclrDiagnose(java.lang.String,java.lang.String,int,java.lang.String,[Ljava
    .lang.String;,java.lang.String,java.lang.String)],Xid=155:94dc41cc01ac93a7(35974
    8176),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=1,seconds since begi
    n=30,seconds left=0,activeThread=Thread[ExecuteThread: '9' for queue: 'default',
    5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connec
    tion]=(state=ended,assigned=none),SCInfo[nckmdomain+nckmsvr]=(state=active),prop
    erties=({weblogic.transaction.name=[EJB com.syscom.prjnckm.hospitalization.decla
    ration.session.DclrMaintainBean.updateDclrDiagnose(java.lang.String,java.lang.St
    ring,int,java.lang.String,[Ljava.lang.String;,java.lang.String,java.lang.String)
    ], weblogic.jdbc=t3://10.10.10.1:80}),OwnerTransactionManager=ServerTM[ServerCoo
    rdinatorDescriptor=(CoordinatorURL=nckmsvr+10.10.10.1:80+nckmdomain+, Resources=
    {})],CoordinatorURL=nckmsvr+10.10.10.1:80+nckmdomain+).: weblogic.ejb20.locks.Lo
    ckTimedOutException: The lock request from EJB:com.syscom.prjnckm.hospitalizatio
    n.declaration.entity.DclrDiagnose with primary key:com.syscom.prjnckm.hospitaliz
    ation.declaration.entity.DclrDiagnosePK@74dfef60 timed-out after waiting 0 ms. T
    he transaction or thread requesting the lock was:Name=[EJB com.syscom.prjnckm.ho
    spitalization.declaration.session.DclrMaintainBean.updateDclrDiagnose(java.lang.
    String,java.lang.String,int,java.lang.String,[Ljava.lang.String;,java.lang.Strin
    g,java.lang.String)],Xid=155:94dc41cc01ac93a7(359748176),Status=Active,numReplie
    sOwedMe=1,numRepliesOwedOthers=1,seconds since begin=30,seconds left=0,activeThr
    ead=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'de
    fault'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=n
    one),SCInfo[nckmdomain+nckmsvr]=(state=active),properties=({weblogic.transaction
    .name=[EJB com.syscom.prjnckm.hospitalization.declaration.session.DclrMaintainBe
    an.updateDclrDiagnose(java.lang.String,java.lang.String,int,java.lang.String,[Lj
    ava.lang.String;,java.lang.String,java.lang.String)], weblogic.jdbc=t3://10.10.1
    0.1:80}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(Coordinat
    orURL=nckmsvr+10.10.10.1:80+nckmdomain+, Resources={})],CoordinatorURL=nckmsvr+1
    0.10.10.1:80+nckmdomain+).
    at weblogic.ejb20.locks.ExclusiveLockManager$LockBucket.lock(ExclusiveLo
    ckManager.java:527)
    at weblogic.ejb20.locks.ExclusiveLockManager.lock(ExclusiveLockManager.j
    ava:258)
    at weblogic.ejb20.manager.ExclusiveEntityManager.acquireLock(ExclusiveEn
    tityManager.java:164)
    at weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveE
    ntityManager.java:219)
    at weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEnti
    tyManager.java:198)
    What it does mean ?
    Could you give me some idea. Thanks you very much.
    imagine
    ps.
    AP server is WLS 6.1 sp1
    all method's tx aattribute is set to Required
    log msg is as following,
    the first time call:
    create diagnose - diagNo=00804
    create diagnose - diagNo=00809
    method complete!!
    the second time call:
    delete diagnose - diagNo=00804
    delete diagnose - diagNo=00809
    create diagnose - diagNo=00804
    method complete!!
    the third time call:
    delete diagnose - diagNo=00804
    create diagnose - diagNo=00804
    create diagnose - diagNo=00809
    method complete!!
    the firth time call:
    delete diagnose - diagNo=00804
    ...then Exception occur

    Thank you Erland. This is what I got from sys.sysprocesses:
    spid 7
    kpid 6544
    blocked 0
    waittype 0x009D
    waittime 489897
    lastwaittype KSOURCE_WAKEUP 
    waitresource
    dbid 1
    uid 1
    cpu 0
    physical_io 0
    memusage 0
    login_time 12-05-2014 21:09
    last_batch 12-05-2014 21:09
    ecid 0
    open_tran 4
    status background                    
    sid 0x0100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    hostname
    program_name
    hostprocess
    cmd SIGNAL HANDLER 
    nt_domain
    nt_username
    net_address
    net_library
    loginame sa
    context_info 0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    sql_handle 0x0000000000000000000000000000000000000000
    stmt_start 0
    stmt_end 0
    request_id 0
    I think I should apply latest service pack and see if the issue exists. 

  • MS SQL Server problem with MDB's: javax.transaction.xa.XAException

              I am programming agents in j2ee and using MDB to implement the asynchronicity of
              the agents.
              Those MDB's get messages (MapMessage) from a controller (an SFSB) that contain
              the agent's ID and the action that the agent has to perform. The MDB creates a
              SFSB, and calls the appropriate action from this session bean. Those actions require
              to read and write from my MS SQL Server 2000 XA database. But when running my
              program, I often get this error, which doesn't seem to affect the action, because
              when I check my database data, everything is updated correctly. So the program
              still completes, but the errors slow down the execution (the program hangs for
              about 3 seconds, each time the error occurs).
              Does anybody has an explanation or solution for this?
              Thank you...
              This is the error output:
              onMessage()
              Reading MapMessage: 1
              <26-apr-2004 14.34 u. CEST> <Error> <EJB> <BEA-010026> <Exception occurred during
              commit of transaction Xid=BEA1-005F88135FFBA636FFF7(15619088),Status=Rolled back.
              [Reason=javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare
              (0) returns -4],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=4,seconds
              left=30,XAServerResourceInfo[JMS_JMS Server2_NotDurable]=(ServerResourceInfo[JMS_JMS
              Server2_NotDurable]=(state=rolledback,assigned=lucille3_ms),xar=JMS_JMS Server2_NotDurable),XAServerResourceInfo[MSSQL
              Connection Pool]=(ServerResourceInfo[MSSQL Connection Pool]=(state=rolledback,assigned=lucille3_ms),xar=MSSQL
              Connection Pool),SCInfo[cluster+lucille3_ms]=(state=rolledback),local properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=lucille3_ms+127.0.0.1:8001+cluster+t3+,
              XAResources={},NonXAResources={})],CoordinatorURL=lucille3_ms+127.0.0.1:8001+cluster+t3+):
              javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare
              (0)returns -4
              at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown
              Source)
              at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.prepare(Unknown Source)
              at weblogic.jdbcx.base.BaseXAResource.prepare(Unknown Source)
              at weblogic.jdbc.jta.DataSource.prepare(DataSource.java:821)
              at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1161)
              at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:395)
              at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              --------------- nested within: ------------------
              weblogic.transaction.RollbackException: Could not prepare resource 'MSSQL Connection
              Pool
              [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare (0) returns -4 - with nested
              exception:
              [javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare
              (0) returns -4]
              at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1644)
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:300)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
              at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
              at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
              at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
              at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
              at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170).>
              

              I am programming agents in j2ee and using MDB to implement the asynchronicity of
              the agents.
              Those MDB's get messages (MapMessage) from a controller (an SFSB) that contain
              the agent's ID and the action that the agent has to perform. The MDB creates a
              SFSB, and calls the appropriate action from this session bean. Those actions require
              to read and write from my MS SQL Server 2000 XA database. But when running my
              program, I often get this error, which doesn't seem to affect the action, because
              when I check my database data, everything is updated correctly. So the program
              still completes, but the errors slow down the execution (the program hangs for
              about 3 seconds, each time the error occurs).
              Does anybody has an explanation or solution for this?
              Thank you...
              This is the error output:
              onMessage()
              Reading MapMessage: 1
              <26-apr-2004 14.34 u. CEST> <Error> <EJB> <BEA-010026> <Exception occurred during
              commit of transaction Xid=BEA1-005F88135FFBA636FFF7(15619088),Status=Rolled back.
              [Reason=javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare
              (0) returns -4],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=4,seconds
              left=30,XAServerResourceInfo[JMS_JMS Server2_NotDurable]=(ServerResourceInfo[JMS_JMS
              Server2_NotDurable]=(state=rolledback,assigned=lucille3_ms),xar=JMS_JMS Server2_NotDurable),XAServerResourceInfo[MSSQL
              Connection Pool]=(ServerResourceInfo[MSSQL Connection Pool]=(state=rolledback,assigned=lucille3_ms),xar=MSSQL
              Connection Pool),SCInfo[cluster+lucille3_ms]=(state=rolledback),local properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=lucille3_ms+127.0.0.1:8001+cluster+t3+,
              XAResources={},NonXAResources={})],CoordinatorURL=lucille3_ms+127.0.0.1:8001+cluster+t3+):
              javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare
              (0)returns -4
              at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown
              Source)
              at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.prepare(Unknown Source)
              at weblogic.jdbcx.base.BaseXAResource.prepare(Unknown Source)
              at weblogic.jdbc.jta.DataSource.prepare(DataSource.java:821)
              at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1161)
              at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:395)
              at weblogic.transaction.internal.ServerSCInfo$1.execute(ServerSCInfo.java:253)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              --------------- nested within: ------------------
              weblogic.transaction.RollbackException: Could not prepare resource 'MSSQL Connection
              Pool
              [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare (0) returns -4 - with nested
              exception:
              [javax.transaction.xa.XAException: [BEA][SQLServer JDBC Driver][SQLServer]xa_prepare
              (0) returns -4]
              at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1644)
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:300)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
              at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
              at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
              at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
              at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
              at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170).>
              

  • Transaction timeouts of 242 seconds

    Hi All,
    I am getting transaction timeouts of 242 seconds. Can somebody help me where
    is this timeout value configured and how change it?
    Here We are Using Weblogic 8.1
    Stateless Session Bean, DAO, Servlets and JSPs
    The log file says as
    <DEBUG>SQLException: The transaction is no longer active - status: 'Marked rollback.
    [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
    after 242 secon
    ds
    Name=[EJB com.hartfordlife.gbd.pvev.ejb.participantadmin.ParticipantAdministrationEJB.getPADownloadCaseCoverage(java.util.ArrayList,java.lang.String,java.lang.String)],Xid=BEA1-003
    0E44EFCA87F28EDB9(14529255),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=242,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue:
    'weblo
    gic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTS
    XAResourceImpl]=(state=started,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@10c624a),SCInfo[mydomain+myserver]=(state=active),properties=({weblogic.transaction.name=[
    EJB com.hartfordlife.gbd.pvev.ejb.participantadmin.ParticipantAdministrationEJB.getPADownloadCaseCoverage(java.util.ArrayList,java.lang.String,java.lang.String)],
    weblogic.jdbc=t3:
    //157.209.165.64:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+157.209.165.64:7001+mydomain+t3+,
    XAResources={},NonXAResources={})],C
    oordinatorURL=myserver+157.209.165.64:7001+mydomain+t3+)]'. No further JDBC access
    is allowed within this transaction.
    <DEBUG>SQLErrorCode: 0
    <DEBUG>SQLState: null
    java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback.
    [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
    after 242 seconds
    Thanks in Advance
    Sai
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Unfortunately, it seems to work different in JBoss7. I created a very simple app and it waits until end of query execution instead of interrupting it.
    I'm porting application from weblogic to JBoss7 and it is critical for me to achieve identical behavior.

  • Database connection error in Weblogic 11g

    Hello Everyone,
    I am new to this forum and Weblogic. I am in the process of migrating a big application from Weblogic 8.1 to Weblogic 11g. I am facing a issue with JDBC Commit. I am getting following exception while trying to commit
    ####<Feb 18, 2010 1:11:51 PM EST> <Debug> <JTAPropagate> <PPXP2CE951B506> <AdminServer> <ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <3de6adeed2d219bd:-1c9bd9a6:126e245ecb6:-7fff-0000000000000010> <1266516711438> <BEA-000000> <java.lang.Exception: DEBUG: receiveRequest, tx=Xid=BEA1-0000957A69A07E5F133C(16499456),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=300,XAServerResourceInfo[demoPool_cashlinkdomain]=(ServerResourceInfo[demoPool_cashlinkdomain]=(state=ended,assigned=none),xar=demoPool,re-Registered = false),SCInfo[cashlinkdomain+AdminServer]=(state=active),properties=({}),local properties=({weblogic.jdbc.jta.demoPool=[autoCommit=false,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=demoPool,appname=null,moduleName=null,connectTime=187,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=false,lastSuccessfulConnectionUse=1266516711423,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
    at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:310)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:344)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:433)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
    at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1584)
    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1357)
    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438)
    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
    at com.mycompany.res.services.util.DatabaseHelper.getConnection(DatabaseHelper.java:109)
    at com.mycompany.res.services.util.DatabaseHelper.getConnection(DatabaseHelper.java:46)
    at com.mycompany.res.services.security.ejb.LoginManagerEJB.login(LoginManagerEJB.java:64)
    at com.mycompany.res.services.security.ejb.LoginManagerEJB_z7om1c_EOImpl.login(LoginManagerEJB_z7om1c_EOImpl.java:573)
    at com.mycompany.res.services.security.ejb.LoginManagerEJB_z7om1c_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
    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(SecurityManager.java:147)
    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)
    ,currentThread=Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={},supportIsValid=true]}),CoordinatorURL=AdminServer+10.240.15.248:7001+cashlinkdomain+t3+)
    at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
    at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.java:1366)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:287)
    at weblogic.rmi.cluster.ClusterableServerRef.dispatch(ClusterableServerRef.java:242)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1138)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1020)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:240)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:882)
    at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:453)
    at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:322)
    at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:298)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    What is going wrong with this?
    I get the following error every time Weblogic is trying to do database connection check
    ####<Feb 18, 2010 1:35:40 PM EST> <Debug> <JTA2PC> <PPXP2CE951B506> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-028CACE03896> <3de6adeed2d219bd:-1c9bd9a6:126e245ecb6:-7fff-00000000000000c6> <1266518140849> <BEA-000000> <BEA1-028CACE03896: JDBC Internal: TX[BEA1-028CACE03896] committing-->committed
    java.lang.Exception: DEBUG
         at weblogic.transaction.internal.TransactionImpl.setState(TransactionImpl.java:1711)
         at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2945)
         at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2737)
         at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2657)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:285)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
         at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:286)
         at weblogic.jdbc.common.internal.ConnectionEnv.testInternal(ConnectionEnv.java:734)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:704)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:487)
         at weblogic.common.resourcepool.ResourcePoolImpl.testResource(ResourcePoolImpl.java:2260)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1601)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1507)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
         at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1942)
         at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:40)
         at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2368)
         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)
    Edited by: user12640178 on Feb 18, 2010 10:36 AM
    Edited by: user12640178 on Feb 18, 2010 10:38 AM

    Priya,
    Thank you so much for your response. I did test my database source from console and on the console it reported the test was successful, where in the admin logs has same exception logs. I did try creating a non XA connection and it did not have these errors. But my application did raise same exception while doing transaction.
    The application has around 250 EJB's that are written long ago and they all comply to EJB 1.1 spec. I am in the process of investigating the level of support for EJB 1.1 in Weblogic 11g.
    - Kasi

  • Transaction Timeout (BPEL v10.1.2.0.0, WebLogic 8.1 sp4)

    We are attempting to process a transform on a medium sized xml doc (~4.5 MB). For the test case we are simply reading the the doc using the FileAdapter, performing a transformation, and then writing the result to a file using the FileAdapter once again. The flow works fine for smallish files (under ~4MB), however, when dropping a file greater than that size the flow fails once finished while writing entries to the BPEL audit log with a TransactionTimedOutException (see exception below).
    I understand what is happening and why (it certainly takes longer than 2 mins to process the file). I have also done quite a bit of digging around for references to this issue and found several posts regarding bumping the transaction timeout value when running the OC4J container. My problem is that we are not running the OC4J container. I know how to manage the default transaction timeout value for WebLogic but it appears that the BPEL application doesn't seem to be honoring the default transaction timeout on the WL Server. I have come to this conclusion for two reasons: first, the default transaction timeout on the WL Server (before modification) is 30 seconds, not the 120 seconds that this transaction is timing out on. second, changing the transaction timeout value on the WebLogic server has no impact on this issue what so ever. I can set the transaction timeout to any value I like, the process ALWAYS times out after 120 seconds.
    Is there another setting on the BPEL server that I may have missed that is overriding the default timeout, i.e. is it possible that when the BPEL server process is starting the transaction it is setting the timeout on the TransactionManager in code prior to starting the transaction?
    Any pointers are greatly appreciated.
    ------------- START STACK TRACE ------------------
    <2007-03-15 13:50:24,625> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Cannot insert audit trail.
    The process domain was unable to insert the current log entries for the instance "10601" to the audit trail table. The exception reported is: The transaction is no longer active - status: 'Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
    Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)]'. No further JDBC access is allowed within this transaction.
    Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usize, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
    <2007-03-15 13:50:24,643> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
    Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1614)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1117)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1881)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1034)
    at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
    at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    ; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 120 seconds
    Name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)],Xid=BEA1-0021B65431A170F9CFEF(31469464),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=120,seconds left=60,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=ended,assigned=none),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@154d033,re-Registered = false),SCInfo[f58_integration+orabpelServer]=(state=active),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(java.lang.String,com.oracle.bpel.client.auth.DomainAuth)], weblogic.jdbc=t3://127.0.0.1:9700}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+, XAResources={},NonXAResources={})],CoordinatorURL=orabpelServer+127.0.0.1:9700+f58_integration+t3+)
    ------------- END STACK TRACE ------------------

    Hi
    i am facing a similar problem..did u find the solution for this problem?
    Please pass the solution/workaround u performed for solving this...
    Thanks & Regards
    Subramanian

  • URGENT!Oracle Type 2 XA Driver(9.2.0.3)problem with EJB on Weblogic 8.1 SP2

    Hi all,
    In our production environment, we're getting the following exception when client requesting the transaction from EJB but it is not happening all the time. It just happens a couple time on day. I assume that it happens 5 out 100 requests.
    Here is the exception...<br>
    <b>================================<br>
    Exception occurred during commit of transaction Name=[EJB com.xxx.xxx.ejb.MappingTrlsBean.getTranslation(java.math.BigDecimal,java.math.BigDecimal,java.math.BigDecimal,java.sql.Date,java.sql.Date)],Xid=BEA1-48F084989933A1C25F07(31980664),Status=Rolled back. [Reason=oracle.jdbc.xa.OracleXAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=76,seconds left=60,XAServerResourceInfo[DS35Pool]=(ServerResourceInfo[DS35Pool]=(state=rolledback,assigned=TTMsvr),xar=DS35Pool),XAServerResourceInfo[DS11Pool]=(ServerResourceInfo[DS11Pool]=(state=rolledback,assigned=TTMsvr),xar=DS11Pool),SCInfo[TTM+TTMsvr]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.bcbsmn.mappingtrls.ejb.MappingTrlsBean.getTranslation(java.math.BigDecimal,java.math.BigDecimal,java.math.BigDecimal,java.sql.Date,java.sql.Date)]}),local properties=({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=TTMsvr+172.16.208.50:6333+TTM+t3+, XAResources={},NonXAResources={})],CoordinatorURL=TTMsvr+172.16.208.50:6333+TTM+t3+): oracle.jdbc.xa.OracleXAException
    <br>...............<br><br>
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Could not prepare resource 'DS35Pool - with nested exception:
    [oracle.jdbc.xa.OracleXAException]
    <br>==============================</b><br>
    I have a couple of connection pools setup called DS35Pool and DS11Pool.
    The configuration of the both driver is
    1)Driver Classname:oracle.jdbc.xa.client.OracleXADataSource
    using ojdbc14.jar from weblogic 8.1 sp2
    2)Remove Infected Connections Enabled is checked
    3)Allow Shrinking is checked with 900 seconds
    4)Test Reserved Connections is checked
    5)Keep XA Connection Till Transaction Complete is checked
    6)Supports Local Transaction is checked.
    Thank you in advance for any help!!!

    That appears to be a bug in the console. You might try the command-line tool java weblogic.Deployer for deploying apps. java weblogic.Deployer -examples will give detailed usage info.
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • Error while updating order - even after using recommended format

    Used below while updating order:
    1) Transaction
    2) Synchronization
    still getting below error:
    Caused by: atg.service.pipeline.RunProcessException: An exception was thrown from the context of the link named [updatePriceInfoObjects].
            at atg.service.pipeline.PipelineChain.runProcess(PipelineChain.java:393)
            at atg.service.pipeline.PipelineChainContext.runProcess(PipelineChainContext.java:207)
            at atg.service.pipeline.PipelineManager.runProcess(PipelineManager.java:475)
            at atg.commerce.pipeline.CommercePipelineManager.runProcess(CommercePipelineManager.java:123)
            at atg.commerce.order.OrderManager.updateOrder(OrderManager.java:2905)
            ... 64 common frames omitted
    Caused by: atg.commerce.CommerceException: Saving order 818320012 failed because doing so would result in data being overwritten. This save attempt had an out of date repository item [pricingAdjustment].
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.writeProperties(ProcSavePriceInfoObjects.java:1428)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.savePricingAdjustments(ProcSavePriceInfoObjects.java:1316)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.saveSubtotalPriceInfos(ProcSavePriceInfoObjects.java:1185)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.saveShippingItemsSubtotalPriceInfos(ProcSavePriceInfoObjects.java:1076)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.savePriceInfo(ProcSavePriceInfoObjects.java:1052)
            at atg.projects.store.order.processor.StoreProcSavePriceInfoObjects.savePriceInfo(StoreProcSavePriceInfoObjects.java:101)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.saveOrderPriceInfo(ProcSavePriceInfoObjects.java:807)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.runProcess(ProcSavePriceInfoObjects.java:716)
            at atg.service.pipeline.PipelineLink.runProcess(PipelineLink.java:255)
            at atg.service.pipeline.PipelineChain.runProcess(PipelineChain.java:365)
            ... 68 common frames omitted
    Caused by: atg.repository.ConcurrentUpdateException: no rows updated oldVersion=1 for item=pricingAdjustment:pa5090009 in GSATransaction=atg.adapter.gsa.GSATransaction@2c6042ec    thread=[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' transaction=Xid=BEA1-439B3F1AD2C4DD758FA4(744502646),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=3600,activeThread=Thread[[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[ATGProductionDS_atgdv02g3]=(ServerResourceInfo[ATGProductionDS_atgdv02g3]=(state=started,assigned=none),xar=ATGProductionDS,re-Registered = false),SCInfo[atgdv02g3+ss_ps01]=(state=active),local properties=({weblogic.jdbc.jta.ATGProductionDS=[autoCommit=true,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=ATGProductionDS,appname=null,moduleName=null,connectTime=38,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=false,lastSuccessfulConnectionUse=1384308810784,secondsToTrustAnIdlePoolConnection=10,currentUser=null,currentThread=null,lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={},supportIsValid=true]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ss_ps01+devrdatgap138.dev.nintendo.com:10180+atgdv02g3+t3+, XAResources={ATGPublishingDS_atgdv02g3, WLStore_atgdv02g3__WLS_ss_ps01, ATGSwitchingDS_A_atgdv02g3, ATGSwitchingDS_B_atgdv02g3, WSATGatewayRM_ss_ps01_atgdv02g3, ATGAgentDS_atgdv02g3, ATGProductionDS_atgdv02g3},NonXAResources={})],CoordinatorURL=ss_ps01+devrdatgap138.dev.nintendo.com:10180+atgdv02g3+t3+)
            at atg.adapter.gsa.GSAItemDescriptor.updateItem(GSAItemDescriptor.java:7507)
            at atg.adapter.gsa.GSARepository.updateItem(GSARepository.java:1075)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.writeProperties(ProcSavePriceInfoObjects.java:1424)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.savePricingAdjustments(ProcSavePriceInfoObjects.java:1316)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.saveSubtotalPriceInfos(ProcSavePriceInfoObjects.java:1187)
            at atg.commerce.order.processor.ProcSavePriceInfoObjects.saveShippingItemsSubtotalPriceInfos(ProcSavePriceInfoObjects.java:1077)
            ... 74 common frames omitted

    Update your Order with the pattern suggested by Devon, here is the link
    Design Pattern for Updating an ATG Order | Devon Hillard&amp;#039;s Digital Sanctuary

  • Maximum open cursors exceeded from Oracle XA Connection pool

    I am on WLS 6.1 sp2.
    When i leave the server up overnight unaccessed and come back and see in the morning,
    I see the following stacktrace on the server console.
    I dont think its causing any harm, but is there anyway to prevent this from occuring?
    java.sql.SQLException: ORA-01000: maximum open cursors exceeded
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oopen.receive(Oopen.java:118)
    at oracle.jdbc.ttc7.TTC7Protocol.open(TTC7Protocol.java:466)
    at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:413)
    at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:432)
    at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:182)
    at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:102)
    at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:86)
    at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection.java:736)
    at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:622)
    at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:163)
    at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
    at weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.java:1032)
    at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:975)
    at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:937)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Hi. I think this is an oracle driver problem, in all likelihood.
    We test a connection with:
    Statement stmt = c.createStatement();
    stmt.execute(sql);
    Where the string sql is "select count(*) from DUAL" if you named your test table as 'DUAL'.
    We obtain no result set, so the driver shouldn't be accruing cursors...
    Can you upgrade to the latest oracle driver?
    Can you upgrade to the latest version of 6.1?
    Jeeva wrote:
    I am on WLS 6.1 sp2.
    When i leave the server up overnight unaccessed and come back and see in the morning,
    I see the following stacktrace on the server console.
    I dont think its causing any harm, but is there anyway to prevent this from occuring?
    java.sql.SQLException: ORA-01000: maximum open cursors exceeded
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oopen.receive(Oopen.java:118)
    at oracle.jdbc.ttc7.TTC7Protocol.open(TTC7Protocol.java:466)
    at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:413)
    at oracle.jdbc.driver.OracleStatement.<init>(OracleStatement.java:432)
    at oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:182)
    at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:102)
    at oracle.jdbc.driver.OracleCallableStatement.<init>(OracleCallableStatement.java:86)
    at oracle.jdbc.driver.OracleConnection.privatePrepareCall(OracleConnection.java:736)
    at oracle.jdbc.driver.OracleConnection.prepareCall(OracleConnection.java:622)
    at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:163)
    at weblogic.jdbc.jta.VendorXAResource.start(VendorXAResource.java:41)
    at weblogic.transaction.internal.ServerResourceInfo.start(ServerResourceInfo.java:1032)
    at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:975)
    at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:937)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • WLS 6.1 The transaction is no longer active...

    Hello guys,
    I have a litle problem. We have an application deployed on WLS 5.1. It is working perfect for more than an year now. We recently migrated to WLS 6.1, which went pretty painlessly. The only problem I figured out is a transaction timeout on one of our EJBs. It's a stateless one and does access a database. The database response time seems to exceed 30 secs and the container just rolls the transaction back and raises an exception:
    The transaction is no longer active (status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
    Name=[EJB com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate()],Xid=46:1c5c7ecedef996e9(6195252),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[npm2000+npm2000_1]=(state=active),properties=({weblogic.transaction.name=[EJB com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate()], weblogic.jdbc=t3://10.72.70.17:7201}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=npm2000_1+10.72.70.17:7201+npm2000+, Resources={})],CoordinatorURL=npm2000_1+10.72.70.17:7201+npm2000+)]). No further JDBC access is allowed  within this transaction.
    com.deuba.pricemodel.sessionbean.FXRateManagerEJB_9hbfr9_Impl populate rolled back. Reason: The transaction is no longer active (status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 seconds
    Name=[EJB com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate()],Xid=46:1c5c7ecedef996e9(6195252),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[npm2000+npm2000_1]=(state=active),properties=({weblogic.transaction.name=[EJB com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate()], weblogic.jdbc=t3://10.72.70.17:7201}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=npm2000_1+10.72.70.17:7201+npm2000+, Resources={})],CoordinatorURL=npm2000_1+10.72.70.17:7201+npm2000+)]). No further JDBC access is allowed  within this transaction.
    java.sql.SQLException: The transaction is no longer active (status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 31 secondsName=[EJB com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate()],Xid=46:1c5c7ecedef996e9(6195252),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[npm2000+npm2000_1]=(state=active),properties=({weblogic.transaction.name=[EJB com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate()], weblogic.jdbc=t3://10.72.70.17:7201}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=npm2000_1+10.72.70.17:7201+npm2000+, Resources={})],CoordinatorURL=npm2000_1+10.72.70.17:7201+npm2000+)]). No further JDBC access is allowed  within this transaction.
            at weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:508)
            at weblogic.jdbc.jts.Statement.getResultSet(Statement.java:408)
            at weblogic.jdbc.rmi.internal.StatementImpl.getResultSet(StatementImpl.java:215)
            at weblogic.jdbc.rmi.SerialStatement.getResultSet(SerialStatement.java:322)
            at com.deuba.pricemodel.pool.FXRatePool.populate(Unknown Source)
            at com.deuba.pricemodel.sessionbean.FXRateManagerEJB.populate(Unknown Source)
            at com.deuba.pricemodel.sessionbean.FXRateManagerEJB_9hbfr9_EOImpl.populate(FXRateManagerEJB_9hbfr9_EOImpl.java:121)
            at jsp_servlet._system._qa.__fx_rate._jspService(__fx_rate.java:290)
            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: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)One problem could be, that the EJBs are compiled with the WLS 5.1 ejbc and also the deployment descriptors are 5.1 compliant. Does anyone have any clue?
    Tx in advance,
    Anton Maleev
    Software Engineer
    Frankfurt
    [email protected]

    Take a look at this link:
    http://e-docs.bea.com/wls/docs61////javadocs/weblogic/management/configuration/JTAMBean.html#getTimeoutSeconds()
    You'll notice the default transaction timeout in WLS 6.1 is 30 seconds. For container managed you
    can set this timeout in the trans-timeout-seconds attribute of the weblogic-ejb-xml.jar file.

  • JMS Send Transaction Failing, due to resources could not be assigned

    I am trying to get a transaction of a JMS send to work where the origination of the send occurs in domain A and the message queue is hosted in domain B. I have been able to get this to work; however, this issue has shown up in recent tests. I haven't changed anything other than the version of the Oracle database client that is being used. I don't see any relationship between that and the persistent store.
    Both domains are hosted on the same computer and both domains are simple development domains. Trust is established between the domains using 'global trust'.
    I'm running Weblogic Server 10.3.4..
    I'm not sure how to get around this issue. I can't find any documentation...
    My suspicion is that there needs to be some special configuration for the transaction, since I'm using the default persistence store. The warnings seem to indicate the problem. The AdminServer is hosted on domain A and the AuditAdminServer on domain B...
    Any assistance will be greatly appreciated!
    Thanks in advance...
    Here is the stacktrace:
    <Apr 11, 2013 11:17:05 AM MDT> <Warning> <JTA> <BEA-110405> <Resource WLStore_audit_domain__WLS_AuditAdminServer was not assigned to any of these servers: AdminServer AuditAdminServer >
    <Apr 11, 2013 11:17:25 AM MDT> <Warning> <JTA> <BEA-110405> <Resource WLStore_audit_domain__WLS_AuditAdminServer was not assigned to any of these servers: AdminServer AuditAdminServer >
    <Apr 11, 2013 11:19:47 AM MDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB gov.va.med.datasharing.core.ServiceBusImpl.processInbound(java.lang.String,java.lang.Object)],Xid=BEA1-003FA101855115C0DB45(13340960),Status=Rolling Back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: WLStore_audit_domain__WLS_AuditAdminServer],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=183,seconds left=22,XAServerResourceInfo[DefaultXADataSource_vhie_domain]=(ServerResourceInfo[DefaultXADataSource_vhie_domain]=(state=rolledback,assigned=AdminServer),xar=DefaultXADataSource,re-Registered = false),XAServerResourceInfo[WLStore_audit_domain__WLS_AuditAdminServer]=(ServerResourceInfo[WLStore_audit_domain__WLS_AuditAdminServer]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[WLStore_vhie_domain_VhieFileStore]=(ServerResourceInfo[WLStore_vhie_domain_VhieFileStore]=(state=rolledback,assigned=AdminServer),xar=WLStore_vhie_domain_VhieFileStore1316539,re-Registered = false),SCInfo[vhie_domain+AdminServer]=(state=rolledback),SCInfo[audit_domain+AuditAdminServer]=(state=rolling-back),properties=({weblogic.transaction.name=[EJB gov.va.med.datasharing.core.ServiceBusImpl.processInbound(java.lang.String,java.lang.Object)]}),local properties=({weblogic.jdbc.jta.DefaultXADataSource=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+192.168.1.120:7001+vhie_domain+t3+, XAResources={WLStore_vhie_domain_VhieFileStore, SDSDataSource_vhie_domain, DefaultXADataSource_vhie_domain, eis/jms/WLSConnectionFactoryJNDIXA, WSATGatewayRM_AdminServer_vhie_domain},NonXAResources={})],CoordinatorURL=AdminServer+192.168.1.120:7001+vhie_domain+t3+): weblogic.transaction.RollbackException: Aborting prepare because the following resources could not be assigned: WLStore_audit_domain__WLS_AuditAdminServer
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1881)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:345)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
         at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:625)
         at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:49)
         at weblogic.ejb.container.internal.BaseRemoteObject.__WL_postInvokeTxRetry(BaseRemoteObject.java:444)
         at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:53)
         at gov.va.med.datasharing.core.ServiceBus_r6xnti_ServiceBusImpl.processInbound(Unknown Source)
         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:597)
         at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)
         at $Proxy89.processInbound(Unknown Source)
         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:597)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
         at $Proxy91.processInbound(Unknown Source)
         at gov.va.med.datasharing.web.ServiceBusDelegate.processInbound(ServiceBusDelegate.java:43)
         at gov.va.med.datasharing.web.adc.PatientServiceImpl.changeADCStatus(PatientServiceImpl.java:58)
         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:597)
         at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:69)
         at org.springframework.expression.spel.ast.MethodReference$MethodValueRef.getValue(MethodReference.java:97)
         at org.springframework.expression.spel.ast.CompoundExpression.getValueInternal(CompoundExpression.java:81)
         at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:102)
         at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:98)
         at org.springframework.binding.expression.spel.SpringELExpression.getValue(SpringELExpression.java:84)
         at org.springframework.webflow.action.EvaluateAction.doExecute(EvaluateAction.java:75)
         at org.springframework.webflow.action.AbstractAction.execute(AbstractAction.java:188)
         at org.springframework.webflow.execution.AnnotatedAction.execute(AnnotatedAction.java:145)
         at org.springframework.webflow.execution.ActionExecutor.execute(ActionExecutor.java:51)
         at org.springframework.webflow.engine.support.ActionTransitionCriteria.test(ActionTransitionCriteria.java:82)
         at org.springframework.webflow.engine.support.TransitionCriteriaChain.test(TransitionCriteriaChain.java:71)
         at org.springframework.webflow.engine.Transition.canExecute(Transition.java:195)
         at org.springframework.webflow.engine.Transition.execute(Transition.java:211)
         at org.springframework.webflow.engine.impl.FlowExecutionImpl.execute(FlowExecutionImpl.java:393)
         at org.springframework.webflow.engine.impl.RequestControlContextImpl.execute(RequestControlContextImpl.java:214)
         at org.springframework.webflow.engine.TransitionableState.handleEvent(TransitionableState.java:119)
         at org.springframework.webflow.engine.Flow.handleEvent(Flow.java:555)
         at org.springframework.webflow.engine.impl.FlowExecutionImpl.handleEvent(FlowExecutionImpl.java:388)
         at org.springframework.webflow.engine.impl.RequestControlContextImpl.handleEvent(RequestControlContextImpl.java:210)
         at org.springframework.webflow.engine.ViewState.handleEvent(ViewState.java:232)
         at org.springframework.webflow.engine.ViewState.resume(ViewState.java:196)
         at org.springframework.webflow.engine.Flow.resume(Flow.java:545)
         at org.springframework.webflow.engine.impl.FlowExecutionImpl.resume(FlowExecutionImpl.java:258)
         at org.springframework.webflow.executor.FlowExecutorImpl.resumeExecution(FlowExecutorImpl.java:169)
         at org.springframework.webflow.mvc.servlet.FlowHandlerAdapter.handle(FlowHandlerAdapter.java:183)
         at org.springframework.webflow.mvc.servlet.FlowController.handleRequest(FlowController.java:174)
         at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
         at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)
         at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)
         at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:915)
         at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:822)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:796)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:180)
         at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: WLStore_audit_domain__WLS_AuditAdminServer
         at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:1153)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2200)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:279)
         ... 77 more
    .>

    It turns out that those packages are, indeed, in extra.
    I didn't think to look there, since I assumed that everything needed by base would be in [core].
    I assumed wrong.

Maybe you are looking for