PK30872; 6.0.2.9: "java.lang.securityexception: attempted commit in subordinate"

Download Description

PK30872 resolves the following problem:

ERROR DESCRIPTION:
In IBM® WebSphere® Application Server V6, the following exception may occur when committing a transaction involving a third-party C++ ORB, such as OmniORB. The problem did not exist with WebSphere Application Server V5.1.

java.lang.SecurityException: Attempted commit in subordinate
at
com.ibm.ws.Transaction.JTA.UserTransactionImpl.commit(UserTransa
ctionImpl.java:248) ...

LOCAL FIX:
none

PROBLEM SUMMARY

USERS AFFECTED:
All WebSphere Application Server version 6.0.2 users.

PROBLEM DESCRIPTION:
"java.lang.SecurityException:
Attempted commit in subordinate" occurs when committing transactions involving third party C++ Orb

RECOMMENDATION:
None

The problem occurs because, upon return from the third party Orb, there was no transaction context present on the response. This caused the transaction service to believe the transaction was still active on the remote server. When the request to commit was made, a check was made to see if the transaction was on-server - this failed, and the resulting SecurityException was thrown.

PROBLEM CONCLUSION:
Class TxClientInterceptor will be changed to handle the case when a response is returned without a transaction context correctly.

The fix for this APAR is currently targeted for inclusion in Fix Pack 6.0.2.17.

Please refer to the Recommended Fixes page for delivery information:
http://www.ibm.com/support/docview.wss?uid=swg27004980

This fix has already been applied to version 6.1.0.