The following is the message i get when i try to perform a JNDI lookup of one of the components in my application.
"Exception caught Exception occured while looking up for one of the Components: RemoteExceptionjava.rmi.RemoteException: Message was not sent because transaction is not active. Xid=BEA1-48906A6CB9F3E9D16004(17266273),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 240 seconds "
Isnt a JNDI lookup operation similar to a read operation ? If so, how do we get a TimeOutException (deadlock like situation) ? The home interface of the remote object is not cached.