WL 6.0 using MS SQL Server 2000 - Transaction timeout when invoking stored procedure

Question

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja

Answer 1

Hi,
Facing a problem on WL6.0. We are connecting to MS SQL server 2000 using a stateless
session bean
using container managed transaction. The bean method does a few updates to the
database and also
calls a stored procedure that generates primary keys many times. This stored procedure
(SP) is running
in a transaction of its own since it has to increment a counter, update the database
and then return the
primary key.The primary key generator SP is working fine and does not lock the
database in many bean
methods.
In some methods we find that the primary key generator SP has locked the database.
We
then see a lock on the database created due to this SP in the MS SQL client. The
execution goes
into the SP and gets stuck there till the bean's transaction times out. The error
message given is
...... .. Exception Message - The transaction is no longer active
(status = Rolling Back. [Reason = weblogic.transaction.internal.TimedOutExcepti
on: Transaction timed out after 31seconds
tx = transaction=(IdHash=1746718,Name = [EJB StructMgrBeanImpl.addStructure()],X
id=10908:51e67e9d7185816a,Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=
0,seconds since begin=31,seconds left=30,activeThread=Thread[ExecuteThread: '7'
for queue: 'default',5,Thread Group for Queue: 'default'],ServerResourceInfo[web
logic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[myserver]=(state
=active),properties=({weblogic.transaction.name=[EJB StructMgrBeanImpl.addStruct
ure()], weblogic.jdbc=t3://10.200.15.136:7001}))]). No further JDBC access is
al
lowed within this transaction.
What could be the potential problems in the method's code/SP that could be causing
the timeout?
Anyone faced similar problems?
Thanks in advance,
Sreeja