WebSphere 7.0 remote client rollback global UserTransaction

Question

I'm observing weird behavior for WebSphere 7.0.0.21:

Architecture:

1. Simple EJB bean with annotation @Local, @Remote Interfaces and transactional method marked as @Required

2. Standalone command line client that looks up remote "jta/usertransaction" and transactional EJB method. Client code starts user transaction, executes method and then tries to rollback it.

Expected behavior: (I see it on Jboss) rollback of DB transaction

Observed behavior: (On WAS 7.0.0.21) commit of DB transaction

I see that client transaction is changing from STATUS_NO_TRANSACTION(6) to STATUS_ACTIVE(0) and then again to STATUS_NO_TRANSACTION(6) after rollback.

I tried to Google it but didn't find any results

Any ideas on this scenario ? I'm pretty much ready to file the issue to IBM.

thanks,

Answer 1

UPDATE:

Finally after long wait and interactions with IBM support I got it resolved:

1. No problems with IBM JRE
2. For Sun/Oracle JRE it requires extra configuration for ORB e.g.

jndiProperties.put("java.naming.corba.orb", com.ibm.CORBA.iiop.ORB.init((String[])null, orbProperties));

and orb.properties from WAS or AppClient JRE is required to be provided as "orbProperties"