EJB Transaction stuck

[Vijay]

Hi All,

I am calling a session EJB's method in a container managed transaction.
In this method, I make a CORBA call to a native code.
The EJB transaction is getting stuck when this method is called some
5000 times in a loop and there seems to be no way to end it. I tried to
configure the Transaction Timeout and Transaction Abandon timeouts but
apart from printing a message in the server console, they're not
actually terminating the transaction.

On the server console, I see these messages:
#################################################
<Dec 12, 2005 1:37:28 PM GMT+05:00> <Error> <WebLogicServer>
<BEA-000337> <ExecuteThread: '3' for queue: 'MyExecuteQueue' has been
busy
for "1,384" seconds working on the request "connection108.session113",
which is more than the configured time (StuckThreadMaxTime) of "600"
seconds.>
<Dec 12, 2005 1:44:54 PM GMT+05:00> <Error> <JTA> <BEA-110423>
<Abandoning transaction after 304 seconds: Name=[EJB com.abc.def.api
.API7Bean.submitJob(java.lang.String,java.io.File,java.lang.String,boolean,java.lang.String,java.io.File,int,java.io.Serializabl
e,java.lang.String,java.lang.String)],Xid=BEA1-41ECEC9EF551(22502512),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=303,seconds
left=-4,SCInfo[mydomain+myserver]=(state=active),properties=({weblogic.transaction.name=[EJB
com.abc.def.api.API7Bean.submitJob(java.lang.String,java.io.File,java.lang.String,boolean,java.lang.String,java.io.File,int,java.io.Serializable,jav
a.lang.String,java.lang.String)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=myserver+10.40.88.147:7001+m
ydomain+t3+, XAResources={},NonXAResources={})])>
#################################################

On server console, in the Execute Threads page, I can see that this
transaction remains there forever without terminating completely. Its
status remains active.

Can you please tell me what are the conditions in which the weblogic
transaction can get stuck and even the timeouts will have no effect on
it?

Thanks for any help,
Vijay

[Vijay]

This is to put into information that if the CORBA connection fails to
release properly, then the EJB transaction can get stuck very badly on
weblogic. Just wondering if weblogic guys can take this up so that at
least rest of the applications remain immune from this stuck
transaction.

Please note that even if I create the new Execute Queue and assign the
hanging thread to it, it still affects the other Execute queues on
which the application is running.