5 Replies Latest reply: May 3, 2004 7:00 AM by 3004 RSS

    ORA-01591: lock held by in-doubt distributed transaction 14.4.44

    3004

      Hi,
      I am using WLI 8.1 SP2 on Windows 2000, Oracle 9.2. I am getting this error...

      <Apr 23, 2004 10:43:43 AM EDT> <Error> <WLW> <000000> <error
      java.io.IOException: [BEA][Oracle JDBC Driver][Oracle]ORA-01591: lock held by
      in
      -doubt distributed transaction 14.4.44

      at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
      at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
      at com.bea.wlw.runtime.core.bean.BMPContainerBean$OracleTableAccess.doSt
      oreByInsert(BMPContainerBean.java:904)
      at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerB
      ean.java:1785)
      at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerB
      ean.java:1742)
      at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContaine
      rBean.java:79)
      at com.bea.wlwgen.PersistentContainer_nga2bb_Impl.ejbStore(PersistentCon
      tainer_nga2bb_Impl.java:149)
      at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(Exclus
      iveEntityManager.java:556)
      at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
      er.java:745)
      at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
      erSCInfo.java:1010)
      at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
      rverSCInfo.java:115)
      at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
      dChain(ServerTransactionImpl.java:1142)
      at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
      ServerTransactionImpl.java:1868)
      at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
      rverTransactionImpl.java:250)
      at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
      sactionImpl.java:221)
      at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
      at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
      java:316)
      at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
      at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
      at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)


      I have tried dropping all wli tables & deleting tlog files (deleting everything
      from cgServer directory). Still get this error.

      Any suggestions??

      TIA
      -Amit
        • 1. Re: ORA-01591: lock held by in-doubt distributed transaction 14.4.44
          3004

          Amit,

          It could be a bug. Open a ticket with BEA and see if they have a patch.

          "Amit Bhutra" <amit@turingconsulting.com> wrote:
          >
          Hi,
          I am using WLI 8.1 SP2 on Windows 2000, Oracle 9.2. I am getting this
          error...

          <Apr 23, 2004 10:43:43 AM EDT> <Error> <WLW> <000000> <error
          java.io.IOException: [BEA][Oracle JDBC Driver][Oracle]ORA-01591: lock
          held by
          in
          -doubt distributed transaction 14.4.44

          at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
          at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
          at com.bea.wlw.runtime.core.bean.BMPContainerBean$OracleTableAccess.doSt
          oreByInsert(BMPContainerBean.java:904)
          at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerB
          ean.java:1785)
          at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerB
          ean.java:1742)
          at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContaine
          rBean.java:79)
          at com.bea.wlwgen.PersistentContainer_nga2bb_Impl.ejbStore(PersistentCon
          tainer_nga2bb_Impl.java:149)
          at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(Exclus
          iveEntityManager.java:556)
          at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
          er.java:745)
          at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
          erSCInfo.java:1010)
          at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
          rverSCInfo.java:115)
          at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
          dChain(ServerTransactionImpl.java:1142)
          at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
          ServerTransactionImpl.java:1868)
          at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
          rverTransactionImpl.java:250)
          at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
          sactionImpl.java:221)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
          at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
          java:316)
          at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
          at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
          at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)


          I have tried dropping all wli tables & deleting tlog files (deleting
          everything
          from cgServer directory). Still get this error.

          Any suggestions??

          TIA
          -Amit
          • 2. Re: ORA-01591: lock held by in-doubt distributed transaction 14.4.44
            3004

            Hello Amit !,
            Lock From In-Doubt Transaction is a 2-p TX issue, A query or DML statement that
            requires locks on a database is probably blocked due to some lock held by a resource
            of an "in-doubt distributed transaction".
            A DB Admin can manually Commit or Rollback an "in-doubt distributed transaction".
            So I suggest you talk to the DBA

            More at : http://www-rohan.sdsu.edu/doc/oracle/server803/A54653_01/ds_ch3.htm

            BTW here's what Oracle says :

            ORA-01591 lock held by in-doubt distributed transaction string

            Cause: An attempt was made to access resource that is locked by a dead two-phase
            commit transaction that is in prepared state.

            Action: The database administrator should query the PENDING_TRANS$ and related
            tables, and attempt to repair network connection(s) to coordinator and commit
            point. If timely repair is not possible, the database administrator should contact
            the database administrator at the commit point if known or the end user for correct
            outcome, or use heuristic default if given to issue a heuristic COMMIT or ABORT
            command to finalize the local portion of the distributed transaction.






            "Sheetal Jain" <sheetal_jain@hotmail.com> wrote:
            >
            Amit,

            It could be a bug. Open a ticket with BEA and see if they have a patch.

            "Amit Bhutra" <amit@turingconsulting.com> wrote:
            Hi,
            I am using WLI 8.1 SP2 on Windows 2000, Oracle 9.2. I am getting this
            error...

            <Apr 23, 2004 10:43:43 AM EDT> <Error> <WLW> <000000> <error
            java.io.IOException: [BEA][Oracle JDBC Driver][Oracle]ORA-01591: lock
            held by
            in
            -doubt distributed transaction 14.4.44

            at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
            at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
            at com.bea.wlw.runtime.core.bean.BMPContainerBean$OracleTableAccess.doSt
            oreByInsert(BMPContainerBean.java:904)
            at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerB
            ean.java:1785)
            at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerB
            ean.java:1742)
            at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContaine
            rBean.java:79)
            at com.bea.wlwgen.PersistentContainer_nga2bb_Impl.ejbStore(PersistentCon
            tainer_nga2bb_Impl.java:149)
            at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(Exclus
            iveEntityManager.java:556)
            at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
            er.java:745)
            at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
            erSCInfo.java:1010)
            at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
            rverSCInfo.java:115)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
            dChain(ServerTransactionImpl.java:1142)
            at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
            ServerTransactionImpl.java:1868)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
            rverTransactionImpl.java:250)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
            sactionImpl.java:221)
            at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
            at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
            java:316)
            at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)


            I have tried dropping all wli tables & deleting tlog files (deleting
            everything
            from cgServer directory). Still get this error.

            Any suggestions??

            TIA
            -Amit
            • 3. Re: ORA-01591: lock held by in-doubt distributed transaction 14.4.44
              3004

              Amit,

              If these problem is happening with the WLI database then I would suggest you should
              talk to BEA support. If it is happening in the application you have built just
              look for any deadlock conditions happening in some scenarios inside different
              inter-related transactions running at the same time, I mean transaction 1 is locking
              something and in the meantime another one B locks something else which is required
              for the transaction A to move farward and now second one needs the resource locked
              by 1st.

              Hope this helps

              "Nagraj Rao" <c_nagraj_rao@hotmail.com> wrote:
              >
              Hello Amit !,
              Lock From In-Doubt Transaction is a 2-p TX issue, A query or DML statement
              that
              requires locks on a database is probably blocked due to some lock held
              by a resource
              of an "in-doubt distributed transaction".
              A DB Admin can manually Commit or Rollback an "in-doubt distributed transaction".
              So I suggest you talk to the DBA

              More at : http://www-rohan.sdsu.edu/doc/oracle/server803/A54653_01/ds_ch3.htm

              BTW here's what Oracle says :

              ORA-01591 lock held by in-doubt distributed transaction string

              Cause: An attempt was made to access resource that is locked by a dead
              two-phase
              commit transaction that is in prepared state.

              Action: The database administrator should query the PENDING_TRANS$ and
              related
              tables, and attempt to repair network connection(s) to coordinator and
              commit
              point. If timely repair is not possible, the database administrator should
              contact
              the database administrator at the commit point if known or the end user
              for correct
              outcome, or use heuristic default if given to issue a heuristic COMMIT
              or ABORT
              command to finalize the local portion of the distributed transaction.






              "Sheetal Jain" <sheetal_jain@hotmail.com> wrote:
              Amit,

              It could be a bug. Open a ticket with BEA and see if they have a patch.

              "Amit Bhutra" <amit@turingconsulting.com> wrote:
              Hi,
              I am using WLI 8.1 SP2 on Windows 2000, Oracle 9.2. I am getting this
              error...

              <Apr 23, 2004 10:43:43 AM EDT> <Error> <WLW> <000000> <error
              java.io.IOException: [BEA][Oracle JDBC Driver][Oracle]ORA-01591: lock
              held by
              in
              -doubt distributed transaction 14.4.44

              at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
              at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
              at com.bea.wlw.runtime.core.bean.BMPContainerBean$OracleTableAccess.doSt
              oreByInsert(BMPContainerBean.java:904)
              at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerB
              ean.java:1785)
              at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerB
              ean.java:1742)
              at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContaine
              rBean.java:79)
              at com.bea.wlwgen.PersistentContainer_nga2bb_Impl.ejbStore(PersistentCon
              tainer_nga2bb_Impl.java:149)
              at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(Exclus
              iveEntityManager.java:556)
              at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
              er.java:745)
              at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
              erSCInfo.java:1010)
              at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
              rverSCInfo.java:115)
              at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
              dChain(ServerTransactionImpl.java:1142)
              at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
              ServerTransactionImpl.java:1868)
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
              rverTransactionImpl.java:250)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
              sactionImpl.java:221)
              at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
              at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
              java:316)
              at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
              at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
              at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)


              I have tried dropping all wli tables & deleting tlog files (deleting
              everything
              from cgServer directory). Still get this error.

              Any suggestions??

              TIA
              -Amit
              • 4. Re: ORA-01591: lock held by in-doubt distributed transaction 14.4.44
                3004

                Getting this problem with WLI. I have just truncated tables and it's fine now.

                Thanks,
                Amit

                "Sheetal Jain" <sheetal_jain@hotmail.com> wrote:
                >
                Amit,

                If these problem is happening with the WLI database then I would suggest
                you should
                talk to BEA support. If it is happening in the application you have built
                just
                look for any deadlock conditions happening in some scenarios inside different
                inter-related transactions running at the same time, I mean transaction
                1 is locking
                something and in the meantime another one B locks something else which
                is required
                for the transaction A to move farward and now second one needs the resource
                locked
                by 1st.

                Hope this helps

                "Nagraj Rao" <c_nagraj_rao@hotmail.com> wrote:
                Hello Amit !,
                Lock From In-Doubt Transaction is a 2-p TX issue, A query or DML statement
                that
                requires locks on a database is probably blocked due to some lock held
                by a resource
                of an "in-doubt distributed transaction".
                A DB Admin can manually Commit or Rollback an "in-doubt distributed
                transaction".
                So I suggest you talk to the DBA

                More at : http://www-rohan.sdsu.edu/doc/oracle/server803/A54653_01/ds_ch3.htm

                BTW here's what Oracle says :

                ORA-01591 lock held by in-doubt distributed transaction string

                Cause: An attempt was made to access resource that is locked by a dead
                two-phase
                commit transaction that is in prepared state.

                Action: The database administrator should query the PENDING_TRANS$ and
                related
                tables, and attempt to repair network connection(s) to coordinator and
                commit
                point. If timely repair is not possible, the database administrator
                should
                contact
                the database administrator at the commit point if known or the end user
                for correct
                outcome, or use heuristic default if given to issue a heuristic COMMIT
                or ABORT
                command to finalize the local portion of the distributed transaction.






                "Sheetal Jain" <sheetal_jain@hotmail.com> wrote:
                Amit,

                It could be a bug. Open a ticket with BEA and see if they have a patch.

                "Amit Bhutra" <amit@turingconsulting.com> wrote:
                Hi,
                I am using WLI 8.1 SP2 on Windows 2000, Oracle 9.2. I am getting
                this
                error...

                <Apr 23, 2004 10:43:43 AM EDT> <Error> <WLW> <000000> <error
                java.io.IOException: [BEA][Oracle JDBC Driver][Oracle]ORA-01591: lock
                held by
                in
                -doubt distributed transaction 14.4.44

                at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
                at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
                at com.bea.wlw.runtime.core.bean.BMPContainerBean$OracleTableAccess.doSt
                oreByInsert(BMPContainerBean.java:904)
                at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerB
                ean.java:1785)
                at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerB
                ean.java:1742)
                at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContaine
                rBean.java:79)
                at com.bea.wlwgen.PersistentContainer_nga2bb_Impl.ejbStore(PersistentCon
                tainer_nga2bb_Impl.java:149)
                at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(Exclus
                iveEntityManager.java:556)
                at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
                er.java:745)
                at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
                erSCInfo.java:1010)
                at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
                rverSCInfo.java:115)
                at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
                dChain(ServerTransactionImpl.java:1142)
                at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
                ServerTransactionImpl.java:1868)
                at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
                rverTransactionImpl.java:250)
                at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
                sactionImpl.java:221)
                at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
                at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
                java:316)
                at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
                at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
                at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
                at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)


                I have tried dropping all wli tables & deleting tlog files (deleting
                everything
                from cgServer directory). Still get this error.

                Any suggestions??

                TIA
                -Amit
                • 5. Re: ORA-01591: lock held by in-doubt distributed transaction 14.4.44
                  3004

                  Hi,

                  I have a similar problem where I get the ORA-1591 error message from our production
                  environment. The testing and production environments both have Bea Weblogic 8.1
                  SP1 and Oracle 9.2.0.0.0.
                  We have never experienced this problem in the test environment, but this error
                  occurs in the production environment at random intervals. The only difference
                  I can see is that our customer have a clustered database. I attach some of the
                  config for the database.

                  The only thing I can find googling on this problem is a similar discussion on
                  the weblogic newsWeb:
                  Newsgroup: to weblogic.developer.interest.transaction
                                                
                                                     

                  Subject:     Re: "in-doubt distributed transaction" (WLS 8.1 SP2/Oracle 9.2.0.4)
                       
                  Date:     Tue, 30 Mar 2004 14:06:11 -0800      
                  From:      Joe Weinstein <joeNOSPAM@bea.com>      
                  Organization:      BEA NEWS SITE      
                  Newsgroup:      weblogic.developer.interest.transaction      
                  Hi. There is a serious bug in the Oracle DBMS (all versions) where in-doubt transactions
                  have their data locked in the DBMS by page rather than by row, so it will indefinitely
                  prevent access to all data on the page, including logically uninvolved data. Oracle
                  understands the problem but currently says they will never fix it (it would take
                  too much work). They offer the alternative that you configure your table data
                  to ensure that no more than one datarow resides on a page. Joe

                  Matt Smith wrote:

                  I've developed an MDB that reads a message from a queue, performs database updates
                  against up to 2 databases, and sends an outgoing JMS message when all is complete.
                  The MDB uses container-managed transactions to ensure that all DB updates and
                  JMS messages are committed or rolled back together. I have had a lot of problems
                  related to transactions failing, becoming "in-doubt" in the database and locking
                  database resources indefinitely.

                  My environment is configured as follows:
                  WebLogic 8.1.2 Server
                  Oracle 9.2.0.4 database with RAC
                  XA Connection Pool with WebLogic Type 2 Oracle Driver OR Oracle 9.2.0.4
                  OCI Driver
                  "Amit Bhutra" <amit@turingconsulting.com> wrote:
                  >
                  Hi,
                  I am using WLI 8.1 SP2 on Windows 2000, Oracle 9.2. I am getting this
                  error...

                  <Apr 23, 2004 10:43:43 AM EDT> <Error> <WLW> <000000> <error
                  java.io.IOException: [BEA][Oracle JDBC Driver][Oracle]ORA-01591: lock
                  held by
                  in
                  -doubt distributed transaction 14.4.44

                  at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
                  at weblogic.jdbc.base.BaseBlobOutputStream.write(Unknown Source)
                  at com.bea.wlw.runtime.core.bean.BMPContainerBean$OracleTableAccess.doSt
                  oreByInsert(BMPContainerBean.java:904)
                  at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerB
                  ean.java:1785)
                  at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerB
                  ean.java:1742)
                  at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContaine
                  rBean.java:79)
                  at com.bea.wlwgen.PersistentContainer_nga2bb_Impl.ejbStore(PersistentCon
                  tainer_nga2bb_Impl.java:149)
                  at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(Exclus
                  iveEntityManager.java:556)
                  at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManag
                  er.java:745)
                  at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(Serv
                  erSCInfo.java:1010)
                  at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(Se
                  rverSCInfo.java:115)
                  at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAn
                  dChain(ServerTransactionImpl.java:1142)
                  at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(
                  ServerTransactionImpl.java:1868)
                  at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(Se
                  rverTransactionImpl.java:250)
                  at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTran
                  sactionImpl.java:221)
                  at weblogic.ejb20.internal.MDListener.execute(MDListener.java:412)
                  at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
                  java:316)
                  at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
                  at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
                  at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)


                  I have tried dropping all wli tables & deleting tlog files (deleting
                  everything
                  from cgServer directory). Still get this error.

                  Any suggestions??

                  TIA
                  -Amit