JTA in Weblogic 5.1 ?

          Can I use JTA and container-managed transactions with Weblogic Server 5.1 or must
          I have Weblogic 6 ?
          Thanks
          Dave
          

Dave,
          You do need to funnel all your SQL through one connection, but WLS 5.1 has the
          machinery to do this transparently for you, in its JTS driver - see Using the JTS
          Driver
          By 1 RM insance, I do mean 1 dbms instance.
          Dave Horner wrote:
          > Hi Peter,
          > Can I just check that to use JTA then, we must put all SQL statements for a single
          > transaction through one connection ( presumably the next transaction's statements
          > can use a new connection ) ?
          > Also, by '1 RM', do you mean a single database manager instance ?
          > Thanks
          > Dave
          >
          > Peter Holditch <[email protected]> wrote:
          > >Dave,
          > >
          > >You can use both, but your updates must all be through a single jdbc connection
          > >to 1
          > >RM instance. The WLS 5.1 infrastructure will enforce this for you, if it
          > >can, or
          > >throw an exception if it can't.
          > >
          > >WLS 6.0 is necessary for a true distributed transaction with 2pc.
          > >
          > >Regards,
          > >Peter.
          > >
          > >Dave Horner wrote:
          > >
          > >> Can I use JTA and container-managed transactions with Weblogic Server
          > >5.1 or must
          > >> I have Weblogic 6 ?
          > >> Thanks
          > >> Dave
          > >
          [att1.html]
          

Similar Messages

  • JTA timeout Weblogic (JMS)

    I have an MDB that reads from a queue quite big messages that are inserted in the database.
    So it's JMS + JDBC so I use JTA.
    On weblogic level I can specify the transaction timeout and set to 10,15 min. (i know is not a good practice for such long transactions but is legacy code)
    I still have worries regarding the JDBC and JMS configuration...: is the JTA overriding the configuration for JDBC or JMS transactions ?
    IF JDBC is configured for a shorter period to timeout ?
    I did not manages to read the specs to see how this should be generally done but i assume is particular from server to server...
    Thanks.

    This provides some information on configuring JTA - http://docs.oracle.com/cd/E21764_01/web.1111/e13731/trxcon.htm#i1054599
    and the administration tasks - http://docs.oracle.com/cd/E21764_01/web.1111/e13731/trxman.htm#i1053371

  • Does weblogic 5.1 support JTA ?

              Hi,
              I am interested in knowing if weblogic 5.1 support JTA.
              Though the EJB1.1 spec speaks of JTA, there is not mention of JTA in weblogic
              5.1 docs.
              THanks
              Jai
              

    WLS 5.1 does support JTA, but it does not support XA or 2PC. These are
              supported in WLS 6.0 and later.
              -- Rob
              kumar J wrote:
              > Hi,
              >
              > I am interested in knowing if weblogic 5.1 support JTA.
              >
              > Though the EJB1.1 spec speaks of JTA, there is not mention of JTA in weblogic
              > 5.1 docs.
              >
              > THanks
              > Jai
              

  • Problem while deploying BPMN to Weblogic

    I am trying to deploy a reasonably complex Oracle BPM application (BPMN) to Weblogic 10.3.4 server installed on RHLinux 5. The issue is I am getting a connection timeout exception in the deployment log and hence the deployment fails.
    After googling through, I tried to increase the timeout value of JTA through weblogic console but this did not help.
    Following is the deployment log in jDeveloper:
    [11:44:33 PM] Preparing to send HTTP request for deployment [11:44:33 PM] Creating HTTP connection to host:localhost, port:7001 [11:44:33 PM] Sending internal deployment descriptor [11:44:33 PM] Sending archive - sca_BPM_rev1.0.jar [12:03:43 AM] Connection to the server timed out. Please check the server log for problems or increase the timeout value. [12:03:43 AM] Error deploying archive sca_BPM_rev1.0.jar to partition "default" on server AdminServer [http://localhost:7001] [12:03:43 AM] HTTP error code returned [-1] [12:03:43 AM] No error message is returned from the server. [12:03:43 AM] Error deploying archive sca_BPM_rev1.0.jar to partition "default" on server AdminServer [http://localhost:7001] [12:03:43 AM] #### Deployment incomplete. ####
    Error log from Weblogic Console:
    May 19, 2011 12:11:28 AM PDT Error oracle.soa.bpel.engine BEA-000000 Unable to activate process IntraFirmTransfer javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds BEA1-0E886C94EA7C131B76F3 at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1748) at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1591) at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1911) at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1501) at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273) 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) ; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds BEA1-0E886C94EA7C131B76F3 at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:154) at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:595) at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:455) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:52) at oracle.bpm.bpmn.engine.ejb.impl.BPMNServerManagerBean_6gbx7k_ICubeServerManagerLocalBeanImpl.deployComponent(Unknown Source) at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:885)
    Can someone throw some hints at the possible causes ?

    · We tried to set the below configurations, but still we are getting same error.
    i. Increased timeout-seconds to 3600 sec in <Oracle Admin console> >>--> Services >>-->JTA.
    ii. Increased timeout-secounds to 3600 sec in OracleBPMWorspace >>-->Coniguration.
    iii. Increased Stuck-Thread Max Time to 14400 sec in Servers>> admin-server >>-->configuration >>-->tuning.
    · Previously the JDeveloper was running in local linux box and weblogic server is running in remote location(@ US). So we thought this may be because of network latency error. Then moved the BPMN project to “weblogic” box itself, still no progre
    AdminServer.log
    ==============
    ####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142257> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: getAllDrivers() Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142257> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142257> <BEA-000000> <[MethodDescriptor] subject: principals=[]>
    ####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142258> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148697> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148697> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148697> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
    ####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148698> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:52:29 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245149483> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
    ####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179748> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179749> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179749> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
    ####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179749> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:53:00 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245180538> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
    ####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202257> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: getAllDrivers() Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202258> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202258> <BEA-000000> <[MethodDescriptor] subject: principals=[]>
    ####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202258> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
    ####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:53:31 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245211595> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
    ####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
    ####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:54:02 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245242648> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
    ####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262257> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: getAllDrivers() Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262257> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262257> <BEA-000000> <[MethodDescriptor] subject: principals=[]>
    ####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262258> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
    ####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
    ####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
    ####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] Access Allowed.
    >
    ####<May 24, 2011 6:54:33 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245273701> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>

  • Weblogic/Java Transaction error...

    Hi,
    have you ever seen an error like this?
    <Dec 15, 2001 2:08:05 AM PST> <Error> <JTA> <Resource weblogic.jdbc.jts.Connection was not assigned to any of these servers: wladm >
    <Dec 15, 2001 2:08:05 AM PST> <Error> <EJB> <Exception during commit of transaction transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Rolled back. [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1325,seconds left=9,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=none),SCInfo[wladm]=(state=rolledback),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})): weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))
         at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1026)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:388)
         at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:791)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:357)
         at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:757)
         at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1261)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:218)
         at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:201)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl.updateUser(UserManagerEjbEOImpl.java:247)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLSkel.invoke(UserManagerEjbEOImpl_WLSkel.java:575)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:115)
         at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:88)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLStub.updateUser(UserManagerEjbEOImpl_WLStub.java:700)
         at com.corrtech.web.admin.ctrl.UserCtrl.updateUser(UserCtrl.java:1022)
         at com.corrtech.web.admin.ctrl.UserCtrl.service(UserCtrl.java:1561)
         at com.corrtech.web.appmain.ctrl.WebRequestDispatcher.dispatch(WebRequestDispatcher.java:246)
         at com.corrtech.web.appmain.ctrl.WebMain.service(WebMain.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    EXCEPTIONadmin2001/12/15;02:08:05.137UserCtrl.updateUser(1035)
    UserCtrl.service(1561)
    WebRequestDispatcher.dispatch(246)
    WebMain.service(48)
    --- exception
    com.corrtech.web.util.WebInternalException: weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))
         at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1026)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:388)
         at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:791)
         at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:357)
         at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:757)
         at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1261)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:218)
         at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:201)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl.updateUser(UserManagerEjbEOImpl.java:247)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLSkel.invoke(UserManagerEjbEOImpl_WLSkel.java:575)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDispatcher.java:115)
         at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:88)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:247)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:225)
         at com.corrtech.usermgmt.app.services.manager.UserManagerEjbEOImpl_WLStub.updateUser(UserManagerEjbEOImpl_WLStub.java:700)
         at com.corrtech.web.admin.ctrl.UserCtrl.updateUser(UserCtrl.java:1022)
         at com.corrtech.web.admin.ctrl.UserCtrl.service(UserCtrl.java:1561)
         at com.corrtech.web.appmain.ctrl.WebRequestDispatcher.dispatch(WebRequestDispatcher.java:246)
         at com.corrtech.web.appmain.ctrl.WebMain.service(WebMain.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ; nested exception is:
         weblogic.transaction.RollbackException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001})) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 31seconds
    tx = transaction=(IdHash=4955751,Name = [EJB UserManagerEjbImpl.updateUser()],Xid=332:84fbe47163d8d80e,Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '95' for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=suspended,assigned=none),SCInfo[wladm]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB UserManagerEjbImpl.updateUser()], weblogic.jdbc=t3://10.10.40.31:7001}))]
         at com.corrtech.web.admin.ctrl.UserCtrl.updateUser(UserCtrl.java:1036)
         at com.corrtech.web.admin.ctrl.UserCtrl.service(UserCtrl.java:1561)
         at com.corrtech.web.appmain.ctrl.WebRequestDispatcher.dispatch(WebRequestDispatcher.java:246)
         at com.corrtech.web.appmain.ctrl.WebMain.service(WebMain.java:48)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    EXCEPTIONadmin2001/12/15;02:08:05.150WebMain.service(53)
    We're using Weblogic 6.1 with Oracle 8.1.6.
    This happens whenever we want to update a record in the database
    represented by our Entity User Ejb object. The weird part is that
    this is the only situacion that causes the problem. We can create
    users without trouble and we can create/update any information in the
    database represented by any of our other beans but update for User is not
    possible.
    I tried to look for information in the bea web site but I could not find
    anything related to it. I couldn't even find the weblogic.jdbc.jts package?
    Do you have any idea about it?
    Thanks in advance.

    Hi Alberto,
    As you can see from the exception the transaction was rolled-back due to timeout. As to your question of why it is happening in the particular method, the reason might be the time that is being taken in this particular operation. You can increase the timeout seconds for the transaction by changing the value in weblogic-ejb-jar.xml file. The default value is 30 secs. Use the tag <trans-timeout-seconds> to change this value. This is the child tag of
    <weblogic-enterprise-bean>
         <transaction-descriptor>
    You can find reference for the tags at http://edocs.beasys.com/wls/docs61/ejb/reference.html#1072610.
    Hope this helps.
    Vikram.

  • Weblogic Server HeuristicMixedException

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

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

  • How to use example of directory 'JTA'

              Hi, I want to know how to use the example of the directory 'JTA'
              uinder the directory of 'JTA' under tthe directory $WL/samples/example/jta
              in order to test the JTA serveice of webloig server ( Futhermore,
              Can anyone can tell me how to config the JTA of weblogic server
              Thanks;
              chris
              

    An Expression is just part of an SQL statement, so you need a query to convert something to SQL. Create a ReadObjectQuery or ReadAllQuery with the Expression, and call,
    query.prepareCall(session, new DatabaseRecord());
    String sql = query.getSQLString();
    (you could also use getTranslatedSQLString(Record) to translate parameter values).
    James : http://www.eclipselink.org

  • Issues with transaction isolation levels (BEA-631 exceptions)

    My intended EJB application will have a session bean that uses two very similar entity beans that will be mapped to different databases; in my test version the entity beans use the same database.
    The final application will need XA transactions with isolation=serializable (beans may be in Oracle, DB2, or MSSQL databases); high probability of concurrent potentially interfering transactions.
    My test example works (Windows XP, WebLogic 8.1, Oracle 9.2) with both BEA's Oracle driver, and the Oracle driver but only when I set a transaction isolation on the session bean as the Oracle specific "transactionreadcommitedforupdate".
    If I try using "transactionserializable", I get an exception like the following when my session-bean first tries to find an entity bean:
    <2/09/2005 10:13:43 AM EST> <Warning> <Common> <BEA-000631> <Unknown resource "weblogic.jdbc.common.internal.ConnectionEnv@1f13e99" being released to pool "BEAOraclePool". Printing out current pool contents.>
    (similar response with both drivers).
    Please could someone explain what is wrong and why setting isolation serializable causes problems. How
    should I fix things?

    Hi. What version of 8.1 is this?
    If you can easily reproduce this
    we may either have a fix, or will
    want to debug this.
    Joe
    Neil Gray wrote:
    The bit about "cleaning up vendor connections" was from the comment by Imeshev that was earlier in this thread.
    The context:
    Application does involve possibility of two concurrent transactions trying to change the same row of a datatable; as isolation level is repeatableread or serializable, this will result in some exceptions. Sometimes exceptions handled ok, sometimes they cause problems.
    Particular case illustrated below is when working with DB2. As I understand it, the two concurrent EJBs both make read requests (presumably acquiring read locks) then make update requests - if they happen to share a row this will block. I don't know enough about DB2 to know what controls its detection of problems. In practice I see db2 typically sending back an error to one of requestors in less than 1 second, but sometimes several seconds may elapse before the error response gets sent (I have observ
    ed actual net traffic).
    If transaction gets timed out in WebLogic (I've curently got a generous 8 second timeout setting in JTA tab) then there are problems.
    First of two exceptions shown here is for normal case where db2 returned an error and it was handled ok:
    11111111111111111
    ####<30/09/2005 10:55:39 AM EST> <Error> <EJB> <ATP-NL2-RS3> <examplesServer> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)],Xid=BEA1-1D5B56A9177C58E3D95B(17477508),Status=Rolled back. [Reason=weblogic.utils.NestedRuntimeException: Error writing from beforeCompletion - with nested exception:
    [weblogic.jdbc.base.BaseBatchUpdateException: [BEA][DB2 JDBC Driver]Abnormal end unit of work condition occurred.]],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=10,XAServerResourceInfo[BEADB2]=(ServerResourceInfo[BEADB2]=(state=rolledback,assigned=examplesServer),xar=BEADB2,re-Registered = false),SCInfo[examples+examplesServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.Bi
    gDecimal)], ISOLATION LEVEL=4}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@eed1b8]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+, XAResources={},NonXAResources={})],CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+): weblogic.jdbc.base.BaseBatchUpdateException: [BEA][DB2 JDBC Driver]Abnormal end unit of work condition occurred.
         at weblogic.jdbc.db2.DB2ImplStatement.executeBatch(Unknown Source)
         at weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    --------------- nested within: ------------------
    weblogic.utils.NestedRuntimeException: Error writing from beforeCompletion - with nested exception:
    [weblogic.jdbc.base.BaseBatchUpdateException: [BEA][DB2 JDBC Driver]Abnormal end unit of work condition occurred.]
         at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:673)
         at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1010)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb20.internal.TxManager$TxListener@eed1b8
    Error writing from beforeCompletion - with nested exception:
    [weblogic.utils.NestedRuntimeException: Error writing from beforeCompletion - with nested exception:
    [weblogic.jdbc.base.BaseBatchUpdateException: [BEA][DB2 JDBC Driver]Abnormal end unit of work condition occurred.]]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    .>
    222222222222222
    Second case is where timeout in WebLogic occurred (I think) which leads to something messing up the connection pool
    ####<30/09/2005 10:56:24 AM EST> <Warning> <Common> <ATP-NL2-RS3> <examplesServer> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <BEA1-22BE56A9177C58E3D95B> <BEA-000631> <Unknown resource "weblogic.jdbc.common.internal.ConnectionEnv@1551d57" being released to pool "BEADB2". Printing out current pool contents.>
    ####<30/09/2005 10:56:24 AM EST> <Warning> <Common> <ATP-NL2-RS3> <examplesServer> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-000631> <Unknown resource "weblogic.jdbc.common.internal.ConnectionEnv@1551d57" being released to pool "BEADB2". Printing out current pool contents.>
    ####<30/09/2005 10:56:24 AM EST> <Warning> <Common> <ATP-NL2-RS3> <examplesServer> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-000631> <Unknown resource "weblogic.jdbc.common.internal.ConnectionEnv@f95d4a" being released to pool "BEADB2". Printing out current pool contents.>
    ####<30/09/2005 10:56:24 AM EST> <Error> <EJB> <ATP-NL2-RS3> <examplesServer> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)],Xid=BEA1-22BD56A9177C58E3D95B(18185360),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 8 seconds
    Name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)],Xid=BEA1-22BD56A9177C58E3D95B(18185360),Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=8,seconds left=10,activeThread=Thread[ExecuteThread: '14' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[BEADB2]=(ServerResourceInfo[BEADB2]=(state=started,assigned=none),xar=BEADB2,re-Registered = false),SCIn
    fo[examples+examplesServer]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)], ISOLATION LEVEL=4}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@1f2a681], weblogic.jdbc.jta.BEADB2=weblogic.jdbc.wrapper.TxInfo@1a4ef37}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+, XAResources={},
    NonXAResources={})],CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+)],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=9,seconds left=9,XAServerResourceInfo[BEADB2]=(ServerResourceInfo[BEADB2]=(state=rolledback,assigned=examplesServer),xar=BEADB2,re-Registered = false),SCInfo[examples+examplesServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)], ISOLATION LEVEL=4})
    ,local properties=({modifiedListeners=[]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+, XAResources={},NonXAResources={})],CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+): weblogic.transaction.internal.TimedOutException: Transaction timed out after 8 seconds
    Name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)],Xid=BEA1-22BD56A9177C58E3D95B(18185360),Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=8,seconds left=10,activeThread=Thread[ExecuteThread: '14' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[BEADB2]=(ServerResourceInfo[BEADB2]=(state=started,assigned=none),xar=BEADB2,re-Registered = false),SCIn
    fo[examples+examplesServer]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)], ISOLATION LEVEL=4}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@1f2a681], weblogic.jdbc.jta.BEADB2=weblogic.jdbc.wrapper.TxInfo@1a4ef37}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+, XAResources={},
    NonXAResources={})],CoordinatorURL=examplesServer+203.143.168.208:7001+examples+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.kernel.ExecuteThread.run(ExecuteThread.java:178)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 8 seconds
    Name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)],Xid=BEA1-22BD56A9177C58E3D95B(18185360),Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=8,seconds left=10,activeThread=Thread[ExecuteThread: '14' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[BEADB2]=(ServerResourceInfo[BEADB2]=(state=started,assigned=none),xar=BEADB2,re-Registered = false),SCIn
    fo[examples+examplesServer]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)], ISOLATION LEVEL=4}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@1f2a681], weblogic.jdbc.jta.BEADB2=weblogic.jdbc.wrapper.TxInfo@1a4ef37}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+, XAResources={},
    NonXAResources={})],CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+) - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 8 seconds
    Name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)],Xid=BEA1-22BD56A9177C58E3D95B(18185360),Status=Active (PrePreparing),numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=8,seconds left=10,activeThread=Thread[ExecuteThread: '14' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[BEADB2]=(ServerResourceInfo[BEADB2]=(state=started,assigned=none),xar=BEADB2,re-Registered = false),SCIn
    fo[examples+examplesServer]=(state=pre-preparing),properties=({weblogic.transaction.name=[EJB db2transferapp.TransferBean.doTransfer(java.lang.String,java.lang.String,java.math.BigDecimal)], ISOLATION LEVEL=4}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@1f2a681], weblogic.jdbc.jta.BEADB2=weblogic.jdbc.wrapper.TxInfo@1a4ef37}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+, XAResources={},
    NonXAResources={})],CoordinatorURL=examplesServer+203.143.168.208:7001+examples+t3+)]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1683)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:325)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    .>
    Once start getting those things released to pool the application falls apart. Shortly afterwards it loses all connections to DB2 (and DB2 may be left with some locks on the table that have to be cleared).
    It isn't DB2 specific, if needed I can supply similar data for MSSQL server (BEA or MS drivers)

  • JMSServer unavailable

    Hi,
    We are using WebLogic 8.1 SP6 in Solaris (Solaris 10 1/06 s10s_u1wos_19a SPARC). JDK 1.4_11.
    We have a clustered environment using two physical servers, with two WebLogic servers per physical server, making a cluster composed by a total of four servers. Our application is deployed in this cluster.
    The application has few JMSServers, being one of them the following:
    <JMSServer Name="EGMSServer@ServerA1" Targets="ServerA1">
    <JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
    ExpirationPolicy="Log"
    JNDIName="jms/Queue1ServerA1"
    Name="Queue1@ServerA1"
    RedeliveryDelayOverride="10000" RedeliveryLimit="1" StoreEnabled="default"/>
    <JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
    ExpirationPolicy="Log"
    JNDIName="jms/Queue2ServerA1"
    Name="Queue2@ServerA1"
    RedeliveryDelayOverride="0" RedeliveryLimit="0" StoreEnabled="default"/>
    <JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
    ExpirationPolicy="Log"
    JNDIName="Queue3ServerA1"
    Name="Queue3@ServerA1"
    RedeliveryDelayOverride="10000" RedeliveryLimit="1" StoreEnabled="default"/>
    <JMSQueue ExpirationLoggingPolicy="%header%,%properties%"
    ExpirationPolicy="Log"
    JNDIName="Queue4ServerA1"
    Name="Queue4@ServerA1"
    RedeliveryDelayOverride="10000" RedeliveryLimit="1" StoreEnabled="default"/>
    </JMSServer>
    Obviously the definition of this JMSServer is repeated for each member of the cluster.
    All worked fine until yesterday at night. We had a big volume of workload and our transactions started to fail due the following reason:
    2007-08-31 05:04:14,775;[ExecuteThread: '4' for queue: 'activity'];trg.TrgService;ERROR;weblogic.jms.common.JMSException: Internal error: XAResource 'JMS_EGJMSServer@ServerA2_NotDurable' is unavailable
    2007-08-31 05:04:14,784;[ExecuteThread: '4' for queue: 'activity'];util.DBService;ERROR;java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: delist() failed on resource 'JMS_EGJMSServer@ServerA2_NotDurable'.
    Internal error: XAResource 'JMS_EGJMSServer@ServerA2_NotDurable' is unavailable
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1604)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1512)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:455)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:410)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:344)
         at DatabaseConnectionPool.getConnection(DatabaseConnectionPool.java:28)
         at Module.getInboundConnection(Module.java:130)
         at DBService.updateIpDataTransmLog(DBService.java:1008)
         at Service.process(bService.java:269)
         at activity.postprocessor.InPostProcessor.processImpl(InPostProcessor.java:88)
         at StageAbs.timebox(StageAbs.java:80)
         at StageAbs.process(StageAbs.java:46)
         at core.bridge.MDBBridgeDelegate.onMessage(MDBBridgeDelegate.java:55)
         at activity.bridge.impl.ejb.EventQueueMDB.onMessage(EventQueueMDB.java:73)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    We observed that few minutes before this problem the JMSServer EGJMSServer became unavailable in the server where the crash took place, and stayed unavailable for 5 minutes. It seems that this unavailability caused this failure. I am including the relevant server logs:
    ####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-110030> <XA resource [JMS_EGJMSServer@ServerA2_NotDurable] has not responded in the last 0 second(s).>
    ####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '1' for queue: 'activity'> <<anonymous>> <BEA1-288E8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
    ####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '2' for queue: 'activity'> <<anonymous>> <BEA1-288C8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
    ####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '3' for queue: 'ctivity'> <<anonymous>> <BEA1-288F8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
    ####<Aug 31, 2007 5:02:26 AM MEST> <Warning> <JTA> <barge> <ServerA2> <ExecuteThread: '4' for queue: 'activity'> <<anonymous>> <BEA1-288D8324BAE684A42059> <BEA-110405> <Resource JMS_EGJMSServer@ServerA2_NotDurable was not assigned to any of these servers: ServerA2 >
    ####<Aug 31, 2007 5:02:26 AM MEST> <Info> <EJB> <barge> <ServerA2> <ExecuteThread: '0' for queue: 'activity'> <<anonymous>> <> <BEA-010213> <Message-Driven EJB: DbSpoolEventQueueMDB's transaction was rolledback. The transaction details are: Xid=BEA1-28908324BAE684A42059(20710803),Status=Rolled back. [Reason=javax.jms.JMSException: failed to enlist the transaction],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,SCInfo[xxx+ServerA2]=(state=rolledback),local properties=({weblogic.jdbc.jta.IntegXAConnectionPool=weblogic.jdbc.wrapper.TxInfo@15eb303}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ServerA2+barge:7032+xxx+t3+, XAResources={JMS_EGJMSServer@ServerA2_NotDurable, JMS_ZZZJMSServer@ServerA2_NotDurable, Sys2ConnectionPool, Sys1ConnectionPool, IntegXAConnectionPool},NonXAResources={})],CoordinatorURL=ServerA2+barge:7032+xxx+t3+).>
    (2.1) ####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '2' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288C8324BAE684A42059(33313611),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable - with nested exception:
    [javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable]
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1687)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    .>
    ####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '3' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288F8324BAE684A42059(21874355),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(ServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(state=started,assigned=none),xar=JMS_EGJMSServer@ServerA2_NotDurable,re-Registered = false),XAServerResourceInfo[IntegXAConnectionPool]=(ServerResourceInfo[IntegXAConnectionPool]=(state=rolledback,assigned=ServerA2),xar=IntegXAConnectionPool,re-Registered =
    ####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '1' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288E8324BAE684A42059(30340443),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(ServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(state=started,assigned=none),xar=JMS_EGJMSServer@ServerA2_NotDurable,re-Registered = false),XAServerResourceInfo[IntegXAConnectionPool]=(ServerResourceInfo[IntegXAConnectionPool]=(state=rolledback,assigned=ServerA2),xar=IntegXAConnectionPool,re-Registered
    ####<Aug 31, 2007 5:02:26 AM MEST> <Error> <EJB> <barge> <ServerA2> <ExecuteThread: '4' for queue: 'activity'> <<anonymous>> <> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-288D8324BAE684A42059(5134189),Status=Rolled back. [Reason=javax.transaction.SystemException: Aborting prepare because the following resources could not be assigned: JMS_EGJMSServer@ServerA2_NotDurable],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(ServerResourceInfo[JMS_EGJMSServer@ServerA2_NotDurable]=(state=started,assigned=none),xar=JMS_EGJMSServer@ServerA2_NotDurable,re-Registered = false),XAServerResourceInfo[IntegXAConnectionPool]=(ServerResourceInfo[IntegXAConnectionPool]=(state=rolledback,assigned=ServerA2),xar=IntegXAConnectionPool,re-Registered =
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    .>
    We have never had this problem and we are clueless about what could have caused it. It was during a moment of a workload pick.
    Could you please advice us on what could be causing this JMSServer to became unavailable? What can justify this problem and wow can we preventit?
    Many thanks!

    Same here. I cannot register for skype manager, it fails on login with the usual:
    "Oops, something went wrong...
    We're having technical problems. We're sorry for the inconvenience. Please try again after a few minutes.
    Thank you."
    Skype heartbeat says everything is ok. Please can we get an update on this?

  • Prod Env prob

    We have Weblogic 8.1 on solaris platform and have a critical application one managed server.This application/server is hangs up quite often ,like 4,5 times in a week.There are 400 execute threads and 3 reader threads.Most of the time the execute threads remain idle ,at the time of problem too, and reader thread are busy.
    I get following Exceptions in log files at different time of problems:
    ####<Feb 7, 2005 8:22:30 AM CST> <Info> <EJB> <lcy002194> <production> <ExecuteThread: '389' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-010049> <EJB Exception in method: remove: java.rmi.NoSuchObjectException: Bean has been deleted..
    java.rmi.NoSuchObjectException: Bean has been deleted.
    at weblogic.ejb20.swap.DiskSwap.read(DiskSwap.java:172)
    at weblogic.ejb20.manager.StatefulSessionManager.getBean(StatefulSessionManager.java:326)
    at weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:396)
    at weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.java:936)
    at weblogic.ejb20.manager.ReplicatedStatefulSessionManager.remove(ReplicatedStatefulSessionManager.java:196)
    at weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:92)
    at com.granite.middle.session.ClientServiceEJB_u5heex_EOImpl.remove(ClientServiceEJB_u5heex_EOImpl.java:4642)
    at com.granite.middle.session.ClientServiceEJB_u5heex_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<Feb 7, 2005 8:23:38 AM CST> <Info> <EJB> <lcy002194> <production> <ExecuteThread: '389' for queue: 'weblogic.kernel.Default'> <<anonymous>> <BEA1-14E3B0CB38DA> <BEA-010051> <EJB Exception occurred during invocation from home: com.granite.middle.worxng.session.Queue_68j9s_HomeImpl@1ec56c9 threw exception: java.lang.NullPointerException
    java.lang.NullPointerException
    at com.granite.middle.worxng.session.QueueBean.getViewPrivilegeQueueList(QueueBean.java:1056)
    at com.granite.middle.worxng.session.Queue_68j9s_EOImpl.getViewPrivilegeQueueList(Queue_68j9s_EOImpl.java:208)
    at com.granite.middle.worxng.session.Queue_68j9s_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java
    ####<Feb 7, 2005 4:50:20 PM CST> <Info> <EJB> <lcy002194> <production> <ExecuteThread: '390' for queue: 'weblogic.kernel.Default'> <<anonymous>> <BEA1-0371ACF1523A94FFBE2B> <BEA-010051> <EJB Exception occurred during invocation from home: com.granite.middle.session.PathEJB_9q5d2l_HomeImpl@f5c440 threw exception: weblogic.utils.NestedError: Unexpected Exception: - with nested exception:
    [java.security.PrivilegedActionException: java.sql.SQLException: Transaction rolled back: Transaction timed out after 599 seconds
    Xid=BEA1-0371ACF1523A94FFBE2B(23844485),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=599,seconds left=60,activeThread=Thread[ExecuteThread: '390' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[JMS_xngJMSFileStore]=(ServerResourceInfo[JMS_xngJMSFileStore]=(state=suspended,assigned=none),xar=JMS_xngJMSFileStore),XAServerResourceInfo[xngprod1_prod]=(ServerResourceInfo[xngprod1_prod]=(state=started,assigned=none),xar=xngprod1_prod),SCInfo[granite+production]=(state=active),local properties=({weblogic.jdbc.jta.xngprod1_prod=weblogic.jdbc.wrapper.TxInfo@d0c4da}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=production+10.174.2.194:7280+granite+t3+, XAResources={},NonXAResources={})],CoordinatorURL=production+10.174.2.194:7280+granite+t3+)]
    java.security.PrivilegedActionException: java.sql.SQLException: Transaction rolled back: Transaction timed out after 599 seconds
    Xid=BEA1-0371ACF1523A94FFBE2B(23844485),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=599,seconds left=60,activeThread=Thread[ExecuteThread: '390' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[JMS_xngJMSFileStore]=(ServerResourceInfo[JMS_xngJMSFileStore]=(state=suspended,assigned=none),xar=JMS_xngJMSFileStore),XAServerResourceInfo[xngprod1_prod]=(ServerResourceInfo[xngprod1_prod]=(state=started,assigned=none),xar=xngprod1_prod),SCInfo[granite+production]=(state=active),local properties=({weblogic.jdbc.jta.xngprod1_prod=weblogic.jdbc.wrapper.TxInfo@d0c4da}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=production+10.174.2.194:7280+granite+t3+, XAResources={},NonXAResources={})],CoordinatorURL=production+10.174.2.194:7280+granite+t3+)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:188)
    at com.granite.middle.helper.jdbc.ConnectionJDBC.getNewConnection(ConnectionJDBC.java:843)
    at com.granite.middle.helper.jdbc.ConnectionJDBC.getConnection(ConnectionJDBC.java:819)
    at com.granite.middle.helper.jdbc.ProfilePrivilegeHelper.checkPrivilege(ProfilePrivilegeHelper.java:553)
    at com.granite.middle.helper.jdbc.ProfilePrivilegeHelper.checkPrivilege(ProfilePrivilegeHelper.java:452)
    at com.granite.middle.logic.PathLogic.getItem(PathLogic.java:429)
    at com.granite.middle.session.PathBean.getItem(PathBean.java:834)
    at com.granite.middle.session.PathBean.getItem(PathBean.java:809)
    at com.granite.middle.session.PathEJB_9q5d2l_EOImpl.getItem(PathEJB_9q5d2l_EOImpl.java:2854)
    at com.granite.bdl.protocol.IIOP.adapter.IIOPPathAdapter.load(IIOPPathAdapter.java:246)
    at com.granite.bdl.protocol.IIOP.adapter.IIOPPathAdapter.loadTransport(IIOPPathAdapter.java:1700)
    at com.granite.bdl.protocol.BDLAdapterImpl.load(BDLAdapterImpl.java:69)
    at com.granite.bdl.protocol.PathImpl.load(PathImpl.java:4656)
    at com.granite.bdl.protocol.PathImpl.loadLiveArchive(PathImpl.java:5004)
    at com.granite.xng_events.DefaultXngEventSerializer.getEventElement(DefaultXngEventSerializer.java:442)
    at com.granite.xng_events.DefaultXngEventSerializer.serialize(DefaultXngEventSerializer.java:92)
    at com.granite.xng_events.XngEventMessageBean.onMessage(XngEventMessageBean.java:442)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    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)
    Caused by: java.sql.SQLException: Transaction rolled back: Transaction timed out after 599 seconds
    Xid=BEA1-0371ACF1523A94FFBE2B(23844485),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,second
    Please provide me some ideas!
    Thanks

    What does your code do at
    com.granite.middle.worxng.session.QueueBean.getViewPrivilegeQueueList, line 1056 ?
    Regards,
    Slava Imeshev
    <syswebadmin> wrote in message news:202461572@jserv5...
    We have Weblogic 8.1 on solaris platform and have a critical application one managed server.This application/server is hangs upquite often ,like 4,5 times in a week.There are 400 execute threads and 3 reader threads.Most of the time the execute threads remain
    idle ,at the time of problem too, and reader thread are busy.
    I get following Exceptions in log files at different time of problems:
    ####<Feb 7, 2005 8:22:30 AM CST> <Info> <EJB> <lcy002194> <production> <ExecuteThread: '389' for queue: 'weblogic.kernel.Default'><<anonymous>> <> <BEA-010049> <EJB Exception in method: remove: java.rmi.NoSuchObjectException: Bean has been deleted..
    java.rmi.NoSuchObjectException: Bean has been deleted.
    at weblogic.ejb20.swap.DiskSwap.read(DiskSwap.java:172)
    at weblogic.ejb20.manager.StatefulSessionManager.getBean(StatefulSessionManager.java:326)
    at weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManager.java:396)
    at weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.java:936)
    at weblogic.ejb20.manager.ReplicatedStatefulSessionManager.remove(ReplicatedStatefulSessionManager.java:196)
    at weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:92)
    at com.granite.middle.session.ClientServiceEJB_u5heex_EOImpl.remove(ClientServiceEJB_u5heex_EOImpl.java:4642)
    at com.granite.middle.session.ClientServiceEJB_u5heex_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<Feb 7, 2005 8:23:38 AM CST> <Info> <EJB> <lcy002194> <production> <ExecuteThread: '389' for queue: 'weblogic.kernel.Default'><<anonymous>> <BEA1-14E3B0CB38DA> <BEA-010051> <EJB Exception occurred during invocation from home:
    com.granite.middle.worxng.session.Queue_68j9s_HomeImpl@1ec56c9 threw exception: java.lang.NullPointerException
    java.lang.NullPointerException
    at com.granite.middle.worxng.session.QueueBean.getViewPrivilegeQueueList(QueueBean.java:1056)
    at com.granite.middle.worxng.session.Queue_68j9s_EOImpl.getViewPrivilegeQueueList(Queue_68j9s_EOImpl.java:208)
    at com.granite.middle.worxng.session.Queue_68j9s_EOImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java
    ####<Feb 7, 2005 4:50:20 PM CST> <Info> <EJB> <lcy002194> <production> <ExecuteThread: '390' for queue: 'weblogic.kernel.Default'><<anonymous>> <BEA1-0371ACF1523A94FFBE2B> <BEA-010051> <EJB Exception occurred during invocation from home:
    com.granite.middle.session.PathEJB_9q5d2l_HomeImpl@f5c440 threw exception: weblogic.utils.NestedError: Unexpected Exception: - with
    nested exception:
    [java.security.PrivilegedActionException: java.sql.SQLException: Transaction rolled back: Transaction timed out after 599 seconds
    Xid=BEA1-0371ACF1523A94FFBE2B(23844485),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=599,seconds
    left=60,activeThread=Thread[ExecuteThread: '390' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue:'weblogic.kernel.Default',XAServerResourceInfo[JMS_xngJMSFileStore]=(ServerResourceInfo[JMS_xngJMSFileStore]=(state=suspended,assigned=none),xar=JMS_xngJMSFileStore),XAServerResourceInfo[xngprod1_prod]=(ServerResourceInfo[xngprod1_prod]=(state=started,assigned=no
    ne),xa
    r=xngprod1_prod),SCInfo[granite+production]=(state=active),localproperties=({weblogic.jdbc.jta.xngprod1_prod=weblogic.jdbc.wrapper.TxInfo@d0c4da}),OwnerTransactionManager=ServerTM[ServerCoordinato
    rDescriptor=(CoordinatorURL=production+10.174.2.194:7280+granite+t3+,
    XAResources={},NonXAResources={})],CoordinatorURL=production+10.174.2.194:7280+granite+t3+)]
    java.security.PrivilegedActionException: java.sql.SQLException: Transaction rolled back: Transaction timed out after 599 seconds
    Xid=BEA1-0371ACF1523A94FFBE2B(23844485),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=599,secondsleft=60,activeThread=Thread[ExecuteThread'390'forqueue'weblogic.kernel.Default',5,ThreadGroupforQueue'weblogic.kernel.Default'],XA
    ServerResourceInfo[JMS_xngJMSFileStore]=,XAServerResourceInfo[xngprod1_prod]=ServerResourceInfo[xngprod1_prod]=state=started,assigne
    d=none,xa
    r=xngprod1_prod),SCInfo[granite+production]=(state=active),localproperties=({weblogic.jdbc.jta.xngprod1_prod=weblogic.jdbc.wrapper.TxInfo@d0c4da}),OwnerTransactionManager=ServerTM[ServerCoordinato
    rDescriptor=(CoordinatorURL=production+10.174.2.194:7280+granite+t3+,
    XAResources={},NonXAResources={})],CoordinatorURL=production+10.174.2.194:7280+granite+t3+)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:188)
    at com.granite.middle.helper.jdbc.ConnectionJDBC.getNewConnection(ConnectionJDBC.java:843)
    at com.granite.middle.helper.jdbc.ConnectionJDBC.getConnection(ConnectionJDBC.java:819)
    at com.granite.middle.helper.jdbc.ProfilePrivilegeHelper.checkPrivilege(ProfilePrivilegeHelper.java:553)
    at com.granite.middle.helper.jdbc.ProfilePrivilegeHelper.checkPrivilege(ProfilePrivilegeHelper.java:452)
    at com.granite.middle.logic.PathLogic.getItem(PathLogic.java:429)
    at com.granite.middle.session.PathBean.getItem(PathBean.java:834)
    at com.granite.middle.session.PathBean.getItem(PathBean.java:809)
    at com.granite.middle.session.PathEJB_9q5d2l_EOImpl.getItem(PathEJB_9q5d2l_EOImpl.java:2854)
    at com.granite.bdl.protocol.IIOP.adapter.IIOPPathAdapter.load(IIOPPathAdapter.java:246)
    at com.granite.bdl.protocol.IIOP.adapter.IIOPPathAdapter.loadTransport(IIOPPathAdapter.java:1700)
    at com.granite.bdl.protocol.BDLAdapterImpl.load(BDLAdapterImpl.java:69)
    at com.granite.bdl.protocol.PathImpl.load(PathImpl.java:4656)
    at com.granite.bdl.protocol.PathImpl.loadLiveArchive(PathImpl.java:5004)
    at com.granite.xng_events.DefaultXngEventSerializer.getEventElement(DefaultXngEventSerializer.java:442)
    at com.granite.xng_events.DefaultXngEventSerializer.serialize(DefaultXngEventSerializer.java:92)
    at com.granite.xng_events.XngEventMessageBean.onMessage(XngEventMessageBean.java:442)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    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)
    Caused by: java.sql.SQLException: Transaction rolled back: Transaction timed out after 599 seconds
    Xid=BEA1-0371ACF1523A94FFBE2B(23844485),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,second
    Please provide me some ideas!
    Thanks

  • XA issue

    We are currently having an issue in are UAT environment where after a some traffic we start seeing the following exceptions when we try specifically to connect to one of our db pools.
    java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 302 seconds
    Xid=BEA1-016D5F6CAC3804D9E1AF(4667487),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=302,seconds left=60,activeThread=Thread[ExecuteThread: '48' for queue: 'weblogic.kernel.Default',5,Thread Group for Queue: 'weblogic.kernel.Default'],XAServerResourceInfo[JMS_cgJMSStore_auto_1]=(ServerResourceInfo[JMS_cgJMSStore_auto_1]=(state=suspended,assigned=none),xar=JMS_cgJMSStore_auto_1,re-Registered = false),XAServerResourceInfo[oradataXAConnectionPool]=(ServerResourceInfo[oradataXAConnectionPool]=(state=started,assigned=none),xar=oradataXAConnectionPool,re-Registered = false),SCInfo[VAGateway+GWServer1]=(state=active),properties=({}),local properties=({weblogic.jdbc.jta.oradataXAConnectionPool=weblogic.jdbc.wrapper.TxInfo@1c624b7}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=GWServer1+155.90.121.72:9999+VAGateway+t3+, XAResources={},NonXAResources={})],CoordinatorURL=GWServer1+155.90.121.72:9999+VAGateway+t3+)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1325)
         at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:183)
         at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:73)
         at weblogic.jdbc.wrapper.ResultSet.checkResultSet(ResultSet.java:108)
         at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:66)
         at weblogic.jdbc.wrapper.ResultSet_weblogic_jdbc_oci_ResultSet.getString(Unknown Source)
         at com.visage.gateway.bean.AssetEntity_sjdkww__WebLogic_CMP_RDBMS.__WL_getPKFromRS(AssetEntity_sjdkww__WebLogic_CMP_RDBMS.java:1190)
         at com.visage.gateway.bean.AssetEntity_sjdkww__WebLogic_CMP_RDBMS.ejbFindBySubscriberEntity_i3l3bq__WebLogic_CMP_RDBMS_asset__WL_(AssetEntity_sjdkww__WebLogic_CMP_RDBMS.java:898)
         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:324)
         at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.collectionFinder(RDBMSPersistenceManager.java:378)
         at weblogic.ejb20.manager.BaseEntityManager.wrapperSetFinder(BaseEntityManager.java:1888)
         at weblogic.ejb20.manager.BaseEntityManager.localWrapperSetFinder(BaseEntityManager.java:1859)
         at com.visage.gateway.bean.SubscriberEntity_i3l3bq__WebLogic_CMP_RDBMS_asset_Set.populateCache(SubscriberEntity_i3l3bq__WebLogic_CMP_RDBMS_asset_Set.java:117)
         at com.visage.gateway.bean.SubscriberEntity_i3l3bq__WebLogic_CMP_RDBMS_asset_Set.size(SubscriberEntity_i3l3bq__WebLogic_CMP_RDBMS_asset_Set.java:596)
         at com.visage.gateway.bean.SubscriberEntity.addAssets(SubscriberEntity.java:212)
         at com.visage.gateway.bean.SubscriberEntity.getSubscriptionVO(SubscriberEntity.java:141)
         at com.visage.gateway.bean.SubscriberEntity_i3l3bq_ELOImpl.getSubscriptionVO(SubscriberEntity_i3l3bq_ELOImpl.java:46)
         at com.visage.gateway.bean.AccountEntity.addSubscribers(AccountEntity.java:145)
         at com.visage.gateway.bean.AccountEntity.getAccountVO(AccountEntity.java:130)
         at com.visage.gateway.bean.AccountEntity_s5203k_EOImpl.getAccountVO(AccountEntity_s5203k_EOImpl.java:993)
         at com.visage.gateway.processes.getCustomerProfile.doGetCustomerProfile(getCustomerProfile.jpd:199)
         at com.visage.gateway.processes.getCustomerProfile_wf$ImplPerform2.invoke(getCustomerProfile_wf.java:54)
         at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
         at com.bea.wli.bpm.runtime.Block.execute(Block.java:39)
         at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
         at com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
         at com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
         at com.visage.gateway.processes.getCustomerProfile_wf$_ProcessState.processMessage(getCustomerProfile_wf.java:176)
         at com.visage.gateway.processes.getCustomerProfile_wf.subscription(getCustomerProfile_wf.java:150)
         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:324)
         at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:367)
         at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
         at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
         at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
         at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
         at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
         at com.bea.wlwgen.getCustomerProfileSLSBContImpl.subscription(getCustomerProfileSLSBContImpl.java:25)
         at com.bea.wlwgen.StatelessContainer_d6ueii_ELOImpl.subscription(StatelessContainer_d6ueii_ELOImpl.java:45)
         at com.bea.wlwgen.getCustomerProfileSLSBContAdpt.invokeOnBean(getCustomerProfileSLSBContAdpt.java:53)
         at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
         at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
         at com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Eventually all the thread get back up and we go into thread starvation.
    Doing a thread dump shows most of the threads stuck at this point.
    "ExecuteThread: '14' for queue: 'weblogic.kernel.Default'" daemon prio=10 tid=000a53d0 nid=27 lwp_id=1507349 waiting for monitor entry [0x2fa39000..0x2fa374f0]
         at weblogic.jdbc.oci.xa.XADataSource.openRM(XADataSource.java:497)
         - waiting to lock <39826628> (a java.lang.String)
         at weblogic.jdbc.oci.xa.XADataSource.open(XADataSource.java:551)
         at weblogic.jdbc.oci.xa.XADataSource.internalStart(XADataSource.java:834)
         at weblogic.jdbc.oci.xa.XADataSource.start(XADataSource.java:830)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:743)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:392)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1509)
         at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1402)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:295)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:451)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:359)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:80)
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1425)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1271)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at com.visage.gateway.util.ServiceLocator.getConnection(ServiceLocator.java:110)
         at com.visage.gateway.phone.InventoryUtility.checkInventory(InventoryUtility.java:205)
         at com.visage.gateway.processes.CheckInventory.perform(CheckInventory.jpd:111)
         at com.visage.gateway.processes.CheckInventory_wf$ImplPerform2.invoke(CheckInventory_wf.java:38)
         at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
         at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
         at com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
         at com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
         at com.visage.gateway.processes.CheckInventory_wf$_ProcessState.processMessage(CheckInventory_wf.java:141)
         at com.visage.gateway.processes.CheckInventory_wf.subscription(CheckInventory_wf.java:115)
         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:324)
         at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:367)
         at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
         at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
         at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
         at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
         at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
         at com.bea.wlwgen.CheckInventorySLSBContImpl.subscription(CheckInventorySLSBContImpl.java:25)
         at com.bea.wlwgen.StatelessContainer_4gsrdx_ELOImpl.subscription(StatelessContainer_4gsrdx_ELOImpl.java:45)
         at com.bea.wlwgen.CheckInventorySLSBContAdpt.invokeOnBean(CheckInventorySLSBContAdpt.java:53)
         at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
         at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
         at com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Any help would be greatfully received.
    David

    Hey Guys
    Changing the oracle driver version resolved the issue.Also there amy be issues with native io vis a vis java io.This was found in another scenario.
    By the way the JTA Time out can be increased if its required
    Cheers
    Saiprasad

  • File not found and exception during commit of transaction

    Hi All,<p></p>
    We are using weblogic 8.1 sp5 and oracle 9.2. In a business process (jpd), I am getting this message and exception immediately after publishing a request document(xml) to a channel and goes to the next process node and the process aborts. Any thoughts are appreciated. Please let me know soon.
    <p></p>
    Thanks in advance!<p></p>
    Prashant
    <p></P>
    <u>Message:</u>
    Could not find a file for class oracle.jdbc.driver.T4CXAConnection
    <p></P>
    If I hit continue while debugging then I get this <u>exception:</u><p></P>
    <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-0049BFC11227BCBD651D(24359063),Status=Rolled back. [Reason=javax.ejb.EJBException: Exception on insert: java.lang.RuntimeException: Unable to serialize invocable],numRepliesOwedMe=0,numR
    epliesOwedOthers=0,seconds since begin=645,seconds left=60,XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=rolledback,assigned=qbAdmin),xar=JMS_cgJMSStore,re-Registered = false),XAServerResourceInfo[cgPool]=(ServerResourceInfo[cgPool]=(state=rolledback,assigned=qbAdmi
    n),xar=cgPool,re-Registered = false),SCInfo[qbDomain+qbAdmin]=(state=rolledback),SCInfo[current+qprocwlp1]=(state=rolledback),properties=({}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@397bfb], weblogic.jdbc.jta.cgPool=weblogic.jdbc.wrapper.TxInfo@4eb65b}),Own
    erTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=qbAdmin+10.1.130.38:7003+qbDomain+t3+, XAResources={JMS_FileStore, JMS_QProcureFileStore, cgPool, JMS_cgJMSStore, bpmArchPool},NonXAResources={})],CoordinatorURL=qbAdmin+10.1.130.38:7003+qbDomain+t3+): javax.ejb.EJBException:
    Exception on insert: java.lang.RuntimeException: Unable to serialize invocable at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1837) at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:193) at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:171) at com.bea.wlwgen.PersistentContainer_bajz39_Impl.ejbStore(PersistentContainer_bajz39_Impl.java:149)at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(ExclusiveEntityManager.java:593) at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:737) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1026) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:116) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1202) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1974) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:257) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430) at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: java.lang.Exception: Exception on insert: java.lang.RuntimeException: Unable to serialize invocable
    at .bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerBean.java:1909) at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1817)... 18 more
    Caused by: java.lang.RuntimeException: Unable to serialize invocable at com.bea.wlw.runtime.core.container.Invocable.toByteArray(Invocable.java:812) at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerBean.java:1859)... 19 more
    Caused by: java.io.NotSerializableException: java.util.AbstractList$ListItr at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at com.bea.wlw.runtime.core.container.Invocable.toByteArray(Invocable.java:803)
    ... 20 more
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb20.internal.TxManager$TxListener@397bfb
    Exception on insert: java.lang.RuntimeException: Unable to serialize invocable - with nested exception:
    [javax.ejb.EJBException: Exception on insert: java.lang.RuntimeException: Unable to serialize invocable] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1684) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430) at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)

    One possible cause of this issue is that your JPD may have some non-transient field(s) which is/are not Serializable. Check for the warnings in the Workshop, that may point you to such fields.
    ~Balwinder

  • EJB - Remote EJB - Transaction Fails to Commit

    I have an SLSB running on an instance of WebLogic 8.1.5 and has a method with a transaction attribute of Required. It calls another SLSB running on another WebLogic 8.1.5 that runs on a remote server and that EJB has a method with a transaction attribute of Required. When the first SLSB completes its call to the second EJB and gets all the data returned back to it, the first SLSB method completes and WebLogic attempts to commit the transaction. When this happens, it appears that the transaction on the second box does not commit and times out. The first SLSB has a transaction timeout of 30 seconds and the second SLSB has a transaction timeout of 500 seconds.
    I found this article that relates to secure communication between WebLogic instances:
    http://forums.bea.com/bea/message.jspa?messageID=400005264&tstart=0
    Our credentials match on both boxes and the -Dweblogic.transaction.SecurityInteropMode=value did not do anything.
    This is the error that we see in our log files:
    [DEBUG] 2007-06-13 08:52:33,766 [ExecuteThread: '23' for queue: 'weblogic.kernel.Default'] com.foo
    .ape.dao.hipaaauth.AuthResponseDAOJdbcImpl : ADDING AuthResponse - SANDB
    OX-488
    [DEBUG] 2007-06-13 08:52:33,776 [ExecuteThread: '23' for queue: 'weblogic.kernel.Default'] com.foo
    .ape.dao.hipaaauth.RejectResponseDAOJdbcImpl : ADDING RejectResponse for e
    vent- 4570 reject type=7B
    javax.transaction.TransactionRolledbackException: Exception while commiting Tx : BEA1-00360416CD7939
    F523D3: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
    0)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
    rverTransactionManagerImpl.java:1147)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
    882)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
    rImpl.java:1064)
    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:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    ; nested exception is:
    weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledback(EJBRuntimeUtils.java:2
    02)
    at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:90)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:343)
    at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
    at com.foo.ape.ejb.ReceiptHandlerSession_p1z9z7_EOImpl.handleEvent(ReceiptHandler
    Session_p1z9z7_EOImpl.java:56)
    at com.foo.ape.web.ReceiptHandlerServlet.doPost(ReceiptHandlerServlet.java:103)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
    a:1072)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
    ontext.java:6985)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:38
    92)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
    0)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
    rverTransactionManagerImpl.java:1147)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
    882)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
    rImpl.java:1064)
    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)
    ... 2 more
    <Jun 13, 2007 8:56:32 AM PDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transa
    ction Name=[EJB com.foo.ape.ejb.ReceiptHandlerSessionEJB.handleEvent(java.lang.String)],X
    id=BEA1-00360416CD7939F523D3(25864837),Status=Rolling Back. [Reason=weblogic.transaction.internal.Ti
    medOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=243,seconds
    left=10,XAServerResourceInfo[medMgmtDbPool]=(ServerResourceInfo[medMgmtDbPool]=(state=rolledback,as
    signed=ccsServer),xar=medMgmtDbPool,re-Registered = false),XAServerResourceInfo[ccsDbPool]=(ServerRe
    sourceInfo[ccsDbPool]=(state=rolledback,assigned=ccsServer),xar=ccsDbPool,re-Registered = false),SCI
    nfo[ccs+ccsServer]=(state=rolledback),SCInfo[DeersDirect2+Deers]=(state=rolling-back),properties=({w
    eblogic.transaction.name=[EJB com.foo.ape.ejb.ReceiptHandlerSessionEJB.handleEvent(java.l
    ang.String)]}),local properties=({weblogic.jdbc.jta.ccsDbPool=weblogic.jdbc.wrapper.TxInfo@c11d39, w
    eblogic.jdbc.jta.medMgmtDbPool=weblogic.jdbc.wrapper.TxInfo@659b02}),OwnerTransactionManager=ServerT
    M[ServerCoordinatorDescriptor=(CoordinatorURL=ccsServer+141.177.53.164:7101+ccs+t3+, XAResources={JM
    S_FileStore, ccsDbPool, medMgmtDbPool, plcDbPool, JMS_jmsStore, pfDbPool, beneDbPool, cmsextDbPool,
    pfuDbPool, pfcDbPool},NonXAResources={})],CoordinatorURL=ccsServer+141.177.53.164:7101+ccs+t3+): web
    logic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
    0)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
    rverTransactionManagerImpl.java:1147)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
    882)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
    rImpl.java:1064)
    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:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3 - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3]
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java
    :1684)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.
    java:311)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:320)
    at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
    at com.foo.ape.ejb.ReceiptHandlerSession_p1z9z7_EOImpl.handleEvent(ReceiptHandler
    Session_p1z9z7_EOImpl.java:56)
    at com.foo.ape.web.ReceiptHandlerServlet.doPost(ReceiptHandlerServlet.java:103)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
    a:1072)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
    ontext.java:6985)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:38
    92)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    .>
    [FATAL] 2007-06-13 08:56:32,037 [ExecuteThread: '23' for queue: 'weblogic.kernel.Default'] com.foo
    .ape.web.ReceiptHandlerServlet : ReceiptHandlerServlet caugh
    t exception javax.transaction.TransactionRolledbackException Exception while commiting Tx : BEA1-003
    60416CD7939F523D3: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123
    seconds
    BEA1-00360416CD7939F523D3
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
    0)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
    rverTransactionManagerImpl.java:1147)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
    882)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
    rImpl.java:1064)
    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:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    ; nested exception is:
    weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3javax.transaction.TransactionRolledbackException: Exception while commiting
    Tx : BEA1-00360416CD7939F523D3: weblogic.transaction.internal.TimedOutException: Transaction timed
    out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
    0)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
    rverTransactionManagerImpl.java:1147)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
    882)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
    rImpl.java:1064)
    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:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    ; nested exception is:
    weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledback(EJBRuntimeUtils.java:2
    02)
    at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:90)
    at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:343)
    at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
    at com.foo.ape.ejb.ReceiptHandlerSession_p1z9z7_EOImpl.handleEvent(ReceiptHandler
    Session_p1z9z7_EOImpl.java:56)
    at com.foo.ape.web.ReceiptHandlerServlet.doPost(ReceiptHandlerServlet.java:103)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
    a:1072)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
    ontext.java:6985)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:38
    92)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
    BEA1-00360416CD7939F523D3
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
    0)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
    rverTransactionManagerImpl.java:1147)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
    882)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
    rImpl.java:1064)
    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)
    ... 2 more

    IIOP is Internet InterORB protocol. The standard from CORBA used for distributed objects communication. This indicates to you that under the covers ejb's use CORBA protocol (iiop). This is so to ensure interoperability between vendors & technologies that invoke distributed objects. t3 is weblogic proprietary. t3 stands fro tengah protocol. Again while using transactions over distributed middleware/over wire then weblogic or any other vendor support iiop over t3 etc. With iiop protocol you are always covered ( as it is industry standard ) while this may not be the case with t3.

  • WLI problem when processing a high number of records - SQLException: Data e

    Hi
    I'm having some trouble with a process in WLI when processing a high number of records from a table. I'm using WLI 8.1.6 and Oracle 9.2.
    The exception I'm getting is:
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.
    I think the problem is not with the table because it's pretty simple. I'll describe the steps in the JPD below.
    1) A DBControl checks to see if the table has records with a specific value in a column.
    select IND_PROCESSADO from VW_EAI_INET_ESTOQUE where IND_PROCESSADO = 'N'
    2) If there is one or more records, we update the column to another value (in other DBControl)
    update VW_EAI_INET_ESTOQUE  set IND_PROCESSADO = 'E' where IND_PROCESSADO = 'N'
    3) We then start a transaction with following steps:
    3.1) A DBControl queries for records in a specific condition
    select
    COD_DEPOSITO AS codDeposito,
    COD_SKU_INTERNO AS codSkuInterno,
    QTD_ESTOQUE AS qtdEstoque,
    IND_ESTOQUE_VIRTUAL AS indEstoqueVirtual,
    IND_PRE_VENDA AS indPreVenda,
    QTD_DIAS_ENTREGA AS qtdDiasEntrega,
    DAT_EXPEDICAO_PRE_VENDA AS dataExpedicaoPreVenda,
    DAT_INICIO AS dataInicio,
    DAT_FIM AS dataFim,
    IND_PROCESSADO AS indProcessado
    from VW_EAI_INET_ESTOQUE
    where IND_PROCESSADO = 'E'
    3.2) We transform all the records found to and XML message (Xquery)
    3.3) We update again update the same column as #2 to other value.
    update VW_EAI_INET_ESTOQUE set  IND_PROCESSADO = 'S'   where IND_PROCESSADO = 'E'.
    4) The process ends.
    When the table has few records under the specified condition, the process works fine. But if we test it with 25000 records, the process fails with the exception below. Sometimes in the step 3.1 and other times in the step 3.3.
    Can someone help me please?
    Exception:
    <A message was unable to be delivered from a WLW Message Queue.
    Attempting to deliver the onAsyncFailure event>
    <23/07/2007 14h33min22s BRT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction
    Xid=BEA1-00424A48977240214FD8(12106298),Status=Rolled back. [Reason=javax.ejb.EJBException: nested
    exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length  1.048.576 specified in create table.],numRepliesOwedMe=0,numRepliesOwedOthers= 0,seconds since begin=118,seconds left=59,XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=rolledback,assigned=cgServer),xar=JMS_cgJMSStore,re-Registered =
    false),XAServ erResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=
    (state=rolledback,assigned=cgServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@d38a58,re-Registered =false),XAServerResourceInfo[CPCasaeVideoWISDesenv]=
    (ServerResourceInfo[CPCasaeVideoWISDesenv]=(state=rolledback,assigned=cgServer),xar=CPCasaeVideoWISDesenv,re-Registered = false),SCInfo[integrationCV+cgServer]=(state=rolledback),
    properties=({weblogic.jdbc=t3://10.15.81.48:7001, START_AND_END_THREAD_EQUAL=false}),
    local properties=({weblogic.jdbc.jta.CPCasaeVideoWISDesenv=weblogic.jdbc.wrapper.TxInfo@9c7831, modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@9c2dc7]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=
    (CoordinatorURL=cgServer+10.15.81.48:7001+integrationCV+t3+,
    XAResources={JMS_FileStore, weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_cgJMSStore, CPCasaeVideoWISDesenv},NonXAResources={})],CoordinatorURL=cgServer+10.15.81.48:7001+integrationCV+t3+): javax.ejb.EJBException: nested exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.
            at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1844)
            at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:227)
            at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:197)
            at com.bea.wlwgen.PersistentContainer_7e2d44_Impl.ejbStore(PersistentContainer_7e2d44_Impl.java:149)
            at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(ExclusiveEntityManager.java:593)
            at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:744)
            at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1069)
            at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:118)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1202)
            at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2007)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:257)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228)
            at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430)
            at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
            at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: javax.ejb.EJBException: nested exception is: java.sql.SQLException: Data exception -- Data -- Input Data length 1.050.060 is greater from the length 1.048.576 specified in create table.
            at com.bea.wlw.runtime.core.bean.BMPContainerBean.doUpdate(BMPContainerBean.java:2021)
            at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1828)
            ... 18 more

    Hi Lucas,
    Following is the information regarding the issue you are getting and might help you to resolve the issue.
    ADAPT00519195- Too many selected values (LOV0001) - Select Query Result operand
    For XIR2 Fixed Details-Rejected as this is by design
    I have found that this is a limitation by design and when the values exceed 18000 we get this error in BO.
    There is no fix for this issue, as itu2019s by design. The product always behaved in this manner.
    Also an ER (ADAPT00754295) for this issue has already been raised.
    Unfortunately, we cannot confirm if and when this Enhancement Request will be taken on by the developers.
    A dedicated team reviews all ERs on a regular basis for technical and commercial feasibility and whether or not the functionality is consistent with our product direction. Unfortunately we cannot presently advise on a timeframe for the inclusion of any ER to our product suite.
    The product group will then review the request and determine whether or not the functionality/feature will be included in a future release.
    Currently I can only suggest that you check the release notes in the ReadMe documents of future service packs, as it will be listed there once the ER has been included
    The only workaround which I can suggest for now is:
    Workaround 1:
    Test the issue by keep the value of MAX_Inlist_values parameter to 256 on designer level.
    Workaround 2:
    The best solution is to combine 'n' queries via a UNION. You should first highlight the first 99 or so entries from the LOV list box and then combine this query with a second one that selects the remaining LOV choices.
    Using UNION between queries; which is the only possible workaround
    Please do let me know if you have any queries related to the same.
    Regards,
    Sarbhjeet Kaur

  • Intermittent XAER_RMERR on Start Branch/ getConnection()

    Hello,
    I've been reading the forums on and off for a couple months now. I was hoping someone could help me with a problem I am facing.
    I have a Container Managed MDB that persists a message in a DB. I am able to successfully complete a XA Transaction and my DB is setup for XA. I am running Weblogic 8 sp3 and connecting to a Oracle 8.1.7 DB using Oracle 9.0.2 drivers (due to integration reasons).
    I ocassionally get the following error. I have "Test Connections on Reserve" and "Test Connections on Release" both checked. My initial Pool size is 0 and I have shrinking allowed. Any thoughts?
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'SMHPMEConnectionPool': XAER_RMERR : A resource manager error has occured in the transaction branch
    javax.transaction.xa.XAException: Unexpected error during start for XAResource 'SMHPMEConnectionPool': Transaction timed out after 61 seconds
    Xid=BEA1-20C1A39CB54A5585B43F(32612847),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=61,seconds left=60,XAServerResourceInfo[JMS_SMHPMEJDBCStore]=(ServerResourceInfo[JMS_SMHPMEJDBCStore]=(state=started,assigned=none),xar=JMS_SMHPMEJDBCStore,re-Registered = false),SCInfo[MLIM+mlimManaged2]=(state=active),local properties=({weblogic.jdbc.jta.SMHPMEConnectionPool=weblogic.jdbc.wrapper.TxInfo@be676c}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=mlimManaged2+jasweblp.mlam.ml.com:9104+MLIM+t3+, XAResources={},NonXAResources={})],CoordinatorURL=mlimManaged2+jasweblp.mlam.ml.com:9104+MLIM+t3+)
         at weblogic.jdbc.wrapper.XA.createException(XA.java:104)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:678)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1103)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1035)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:213)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:461)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1383)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1325)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:396)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:354)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
         at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.getConnection(Unknown Source)
         at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.init(Unknown Source)
         at com.ml.mlim.smh.pme.portfolio.j2ee.PMEPortfolioBean.onMessage(Unknown Source)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    You might try upping your JTA Transaction Timeout as well
    as XASetTransactionTimeout and XATransactionTimeout; the
    latter have to be set manually in the config.xml.
    I believe we had similar problems with long-running txns,
    and this fixed it.
    : jay

Maybe you are looking for

  • Combining tracks into one album, choosing track order

    Hi, I've searched this forum and haven't been able to solve this yet. I have a bunch of b-sides that I want to add to an album proper. Say the album has 12 tracks. I am able to add an additional song to the album, which increases the track count to 1

  • Data target problem

    Hi, I am learning BW now. I am in an attempt of doing activation of Business content(area :personnel development-infosource (0HR_PA_PD_2),data source(0HR_PA_PD_2)),while doing I am getting the following error message; "No data targets have yet been u

  • Undo Shortcut not working across CC

    I have a fully updated version of CC running on Mountain Lion and today the Undo shortcut (Command + Z) doesn't want to work. I can go up to the menu and go Edit > Undo, but I'd rather not! Does anyone know what the issue might be? It's not working a

  • Unauthorised use of this FTP server ( 530)

    Hello, By accessing the Apex the following message is displayed: "220 - serv-tst Unauthorised use of this FTP server is prohibited and may be subject to civil and criminal prosecution. 220 serv-tst FTP Server (Oracle XML DB / Oracle Database) ready.

  • Bridge no localiza Photoshop tras actualizar a CC 2014

    Tras actualizar a Photoshop CC 2014 Bridge no localiza el directorio de Photoshop y da un error Como cambiar la ruta de acceso ya que ahora esta en otro directorio?