Transaction Problem - Timeout

Question

Folks
I am experiencing a Transaction timeout error on a supposed non-transacted method.
Here's the scoop. The Stateless Session bean MemberManager has the Transaction
Attribute set either as "SUPPORTS" or "REQUIRED". Gets and Finds are set to "SUPPORTS"
The Entity beans MemberBean and PolicyHolderBean have all method transaction
attributes set to SUPPORTS. As you can tell transaction mgt is handled at the
SBlevel.
<container-transaction>
<method>
<ejb-name>MemberManager</ejb-name>
<method-name>getMemberModel</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>MemberBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>PolicyHolderBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
The call to MemberManager.getMemberModel is thus non-transacted. Yet I recieve
(from time to time) a Transaction timeout on the PolicyHolderBean.findByPrimaryKey.
(FYI there is a 1:1 CMR relationship between Member and PolicyHolder). The stack
trace follows. Any help is appreciated. Why is this being transacted?
####<Sep 23, 2002 2:12:43 PM EDT> <Error> <com.hmcng.service.job.AbstractJob>
<HMCAPPSVR3> <NextGen3> <Thread-111> <> <21104:3b4203690f8f04a5> <000000> <abstractjob.generate.exception.exception:
letterservice.updatejobstatuserror.remoteexception: Message was not sent because
transaction is not active. Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Rolled
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed
out after 33 seconds
Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[hmc_letters+NextGen3]=(state=active),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=66,seconds left=10,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=NextGen3),SCInfo[hmc_letters+NextGen3]=(state=rolledback),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)>
####<Sep 23, 2002 2:12:43 PM EDT> <Error> <com.hmcng.service.job.AbstractJob>
<HMCAPPSVR3> <NextGen3> <Thread-111> <> <21104:3b4203690f8f04a5> <000000> <abstractjob.generate.exception:
memberservice.getmembermodel.remoteexception: member.unable.to.find.member: Problem
in findByPrimaryKey while preparing or executing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@14b404':
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 33 seconds
Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[hmc_letters+NextGen3]=(state=active),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)]). No further
JDBC access is allowed within this transaction.
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 33 seconds
Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[hmc_letters+NextGen3]=(state=active),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)]). No further
JDBC access is allowed within this transaction.
at weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:508)

Answer 1

          "Jeremy Meyer" <[email protected]> wrote:
          >I am running WL 6.0 on Win NT 4.0 SP 6
          >
          >I am having a problem with a transaction timing out while doing some stuff
          >with EJBs. They do some calculations that can take a few minutes and thus
          >the transactions must last that long but they are timing out after 30
          >seconds. I went to the console and changed the timeout time to a higher
          >setting. This seemed to work but then when I did the same thing a little
          >while later it timed out after 30 seconds again. I look at the console and
          >it says the timeout time is 180 seconds. Any thoughts on what I am doing
          >wrong/why it is acting this way? Thanks.
          Ugh. This is a known problem. As it turns out, EJB's deployment descriptor defaults
          to 30 seconds if a timeout value is not specified. It then overrides the JTA subsystem's
          default timeout settings.
          The workaround is to always specify a valid transaction timeout in the EJB's DD,
          and not to let it default.
          -Sriram