Doubts on weblogic transaction

Question

          Hi,
          I have done a testing on transaction, and found something strange:
          when the transcation timeout, I found there were two thread running and not released:
          1. the thread running the transaction(even the transaction was timeout, this thread
          was still running, why?);
          2. the thread which was running:weblogic.transaction.internal.TransactionImpl$1(why
          consume another thread in "default" queue to run the job,and for what? )
          3. what happened to that DB connection, will it be returned to pool again?Can
          it be used again?
          Thanks
          

Answer 1

          Hi, Joseph:
          here is the thread dump:
          "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0xf2cee20 nid=0x6f0
          waiting for monitor entry [0x1054f000..0x1054fdc0]
               at oracle.jdbc.driver.OracleConnection.rollback(OracleConnection.java:1364)
               at weblogic.jdbc.jts.Connection.internalRollback(Connection.java:806)
               at weblogic.jdbc.jts.Connection.rollback(Connection.java:516)
               at weblogic.transaction.internal.ServerResourceInfo.rollback(ServerResourceInfo.java:1416)
               at weblogic.transaction.internal.ServerResourceInfo.rollback(ServerResourceInfo.java:671)
               at weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.java:394)
               at weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:1538)
               at weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2164)
               at weblogic.transaction.internal.TransactionImpl$1.execute(TransactionImpl.java:1673)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
          "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0xf1708a0 nid=0x6f8
          runnable [0x1050f000..0x1050fdc0]
               at oracle.jdbc.oci8.OCIDBAccess.do_execute(Native Method)
               at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java:1732)
               at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2053)
               at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
               at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
               at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
               at weblogic.jdbc.jts.Statement.executeUpdate(Statement.java:509)
               at jsp_servlet.__test_jdbc._jspService(__test_jdbc.java:111)
               at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
               at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
          Thanks&Regards
          >
          >
          >lumin wrote:
          >
          >> After the transaction timeout, I monitor through weblogic console and
          >get the thread
          >> message:
          >>
          >> thead 8 still running, Http Request: /life/test_jdbc.jsp {weblogic.transaction.internal.JTATransactionImpl:
          >> name=null, xid=2:e33999517f28edb9, status=Rolling Back. [Reason=weblogic.transaction.internal.TimedOutException:
          >> Transaction timed out after 30 seconds Xid=2:e33999517f28edb9(8304246),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          >> since begin=30,seconds left=30,activeThread=Thread[ExecuteThread: '8'
          >for queue:
          >> 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none,xar=weblogic.jdbc.jts.Connection@7d1491),SCInfo[mydomain+myserver]=(state=active),properties=({weblogic.jdbc=t3://172.16.6.2:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+172.16.6.2:7001+mydomain+t3+,
          >> Resources={})],CoordinatorURL=myserver+172.16.6.2:7001+mydomain+t3+)],
          >userProperties={weblogic.jdbc=t3://172.16.6.2:7001},
          >> secondsActive=103, servers=myserver, resourceNamesAndStatus=weblogic.jdbc.jts.Connection/started}
          >>
          >>
          >> thread 7 is also running: weblogic.transaction.internal.TransactionImpl$1@1f1321
          >>
          >>
          >> When I rollback the delete operation, thread 7 disappear first, after
          >a while,
          >> thread 8 also disapper.
          >> But if I let it be, thread 7 and thread 8 will not stop running.
          >
          >Ok. Oracle's driver is unable to interrupt certain DBMS activity, even
          >if a
          >rollback is called on the connection. However, please duplicate the hanging,
          >and please show me the full stack trace of the two hanging threads.
          >thanks,
          >Joe
          >
          >>
          >>
          >> Thanks&Regards
          >> >
          >> >
          >> >lumin wrote:
          >> >
          >> >> Hi, Joseph:
          >> >>
          >> >> Thanks for your revert.Here is the platform information for testing:
          >> >>
          >> >> operating system:Windows2000 professional
          >> >> app server: weblogic 7.0 sp4
          >> >> database client: oracle 9.2.0.1
          >> >> DB driver: Oracle OCI driver
          >> >> what am I doing: delete a record from command line and didn't commit/rollback;
          >> >> then running a JSP program which trying to update the deleted record.
          >> >
          >> >Ok, and what happens when you comit or rollback the SQL-PLUS session?
          >> >Joe
          >> >
          >> >>
          >> >>
          >> >> Thanks&Regards.
          >> >>
          >> >> >
          >> >> >lumin wrote:
          >> >> >
          >> >> >> Hi,
          >> >> >>
          >> >> >> I have done a testing on transaction, and found something strange:
          >> >> >>
          >> >> >> when the transcation timeout, I found there were two thread running
          >> >> >and not released:
          >> >> >>
          >> >> >> 1. the thread running the transaction(even the transaction was
          >timeout,
          >> >> >this thread
          >> >> >> was still running, why?);
          >> >> >> 2. the thread which was running:weblogic.transaction.internal.TransactionImpl$1(why
          >> >> >> consume another thread in "default" queue to run the job,and
          >for
          >> >what?
          >> >> >)
          >> >> >> 3. what happened to that DB connection, will it be returned to
          >pool
          >> >> >again?Can
          >> >> >> it be used again?
          >> >> >>
          >> >> >> Thanks
          >> >> >
          >> >> >Hi. Depending on what DBMS and what JDBC driver you are using,
          >and
          >> >what
          >> >> >the JDBC Connection is doing at the time, it may not return from
          >it's
          >> >> >activity
          >> >> >even though we've sent a rollback() to the connection. What version
          >> >of
          >> >> >the server
          >> >> >are you using?
          >> >> >Joe
          >> >> >
          >> >> >
          >> >
          >