OC4J CMT creates multiple transactions

Question

Hi
This is in continuation to the post : Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back t and
Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back
I have two stateless session beans (EJB1 and EJB2) both
- are set to be transaction-type = container and
- trans-attribute = required
Both EJBs need to participate in the same transaction and use Oracle9iJTSExternalTransactionController (details are in the above mentioned thread).
When method is invoked on EJB1 it is starting a transaction and all subsequent calles to EJB2 are opening a new transactions. Here is what I have done to test it out.
I wrote a following method that is being called from all EJB methods.
private void printTxnInContext(String methodName)
try{
InitialContext initialcontext = new InitialContext();
String jndiName = "java:comp/pm/TransactionManager";
TransactionManager manager = (TransactionManager) initialcontext.lookup(jndiName);
System.out.println(" Transaction for :" + methodName + ":" + manager.getTransaction());
System.out.println(" Transaction Hashcode for :" + methodName + ":" + manager.getTransaction().hashCode());
}catch(Exception e)
e.printStackTrace();
And This is what I found
(Hashcodes):
05/12/06 21:39:49 Transaction Hashcode for :addMergeRequest:23484941
05/12/06 21:39:49 Transaction Hashcode for :addNewProcess:15938176
05/12/06 21:39:50 Transaction Hashcode for :activateTask:30698528
(ToString)
05/12/06 21:39:49 Transaction for :addMergeRequest:[Transaction a4:a2:dc:48:0:0:0:0:9:0:0:0:0:0:0:0:0:a:1:8:3:16:c4:30]
05/12/06 21:39:49 Transaction for :addNewProcess:[Transaction a4:a2:dc:48:0:0:0:0:a:0:0:0:0:0:0:0:0:b:1:8:3:16:c4:62]
05/12/06 21:39:50 Transaction for :activateTask:[Transaction a4:a2:dc:48:0:0:0:0:d:0:0:0:0:0:0:0:0:e:1:8:3:16:c7:d3]
Any help is appreaciated.
Thanks
Raju

Answer 1

Doug, Andrei and others
I found the problem. I have a Delegate that provides access to all EJBS. This delegate is used by both the webtier and middle tier.It is written in a generic fashion so that the web server and middle tier does not have to be co-located in one container. getInitialContext() which is implemented as follows:
private static Context getInitialContext() throws NamingException
// Get InitialContext for Embedded OC4J.
// The embedded server must be running for lookups to succeed.
// actual code reads from the external parameters
String contextFactory = "com.evermind.server.rmi.RMIInitialContextFactory";
String principal = "admin";
String passwd = "admin123";
String providerURL = "ormi://localhost:3201/shc";
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, contextFactory);
env.put(Context.SECURITY_PRINCIPAL, principal);
env.put(Context.SECURITY_CREDENTIALS, passwd);
env.put(Context.PROVIDER_URL, providerURL);
env.put("dedicated.rmicontext","true");
return new InitialContext(env);
When the EJB1 tries to look up for EJB2, container thinks that the call is from outside the container and it is starting a new transaction.
When I changed the EJB1 to look up EJB2 to get the context as shown below,every thing seems to rolling back.
private static Context getInitialContext() throws NamingException
return new InitialContext();
Thanks again for pointing me in the right direction.
I will post the same message in other threads.
Raju