TimedOutException exception when call an EJB in an other container

Question

Hi there,
I am encountering a strange problem after I moved from WLS5.1 to
WLS6.1SP2.
There are two 6.1 app servers and two stateless session beans involved
in our problem. The scenario is the following:
EJB1 has RequiresNew on all methods as TRX attribute
EJB2 has NotSupported on all methods as TRX attribute
client calls method_1 on EJB1 in Server1
EBJ1 method_1 calls method_2 on EJB2 in Server2
EJB1 method returns
The client does not return from his call to EJB1 until a
'weblogic.transaction.internal.TimedOutException' occurs on the
server. In the debugger I can see that method_1 in EJB1 and method_2
in EJB_2 actually return successfully.
This behaviour can easily be fixed by setting the TRX attributes to
NotSupported on EJB1 as well, but I think this is not correct.
Any ideas?
Thanks
Juerg

Answer 1

Hi Li,
If you would like to keep the generated source you start your oc4j using this command.
java -jar -DKeepWrapperCode=true oc4j.jar
And the null pointer might not have occured from the the create method, but i feel the home object is null in the thread which is calling this method.
--Shrini