PM88789: "COMMIT IN SUBORDINATE" ERROR WHEN USING ENABLEINPROCESSCONNECTIONS = TRUE

Fixes are available

APAR status

Closed as program error.

Error description

When JVM custom property enableInProcessConnections = true is
set, error similar to the following is seen:

[2/15/13 18:08:55:661 GMT] 000000f0 UserTransacti <  commit
(API) Exit
                                 java.lang.SecurityException:
Attempted commit in subordinate


The error is specific to the use if enableInProcessConnections
with a multiple nested web services that utilise bean managed
transactions. As each web service is called in this
environment, the thread's transaction context is cleared and
suspended. If this occurs multiple times, it is not possible to
restore the transaction context, and so transactions are not
resolved as the web services exit, leading to the "commit in
subordinate" error, as the transaction service still has
suspended transactions.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who make use of web service          *
*                  transactions and                            *
*                  enableInProcessConnections                  *
****************************************************************
* PROBLEM DESCRIPTION: Failure to commit transaction when      *
*                      using enableInProcessConnections        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Transactions can fail to commit if web service transactions
(WS-AT) are in use with web container property
enableInProcessConnections.
The enableInProcessConnections property optimises the code
path for web services called within the same JVM. This means
that if a web service calls a further web service the same
thread
is used instead of invoking the HTTP interface. When a series
of services are used that make use of bean-managed
transactions, the transaction context is lost after the second
invocation. This prevents transactions from being resolved as
the web service calls return, and so a transaction remains
suspended as it is committed.

Problem conclusion

The WS-AT code has been updated to correctly track multiple
transaction suspensions occurring on the same thread.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.47, 7.0.0.31, 8.0.0.8 and 8.5.5.1.  Please refer
to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM88789
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-10
Closed date
2013-06-26
Last modified date
2013-06-26

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM93499

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022

Tips

PM88789: "COMMIT IN SUBORDINATE" ERROR WHEN USING ENABLEINPROCESSCONNECTIONS = TRUE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?