Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
EJB requests sent from a client application on WebSphere Application Server on z/OS to a clustered EJB on WebSphere Application Server on a distributed platform (Linux, AIX, Solaris, HP-UX, or Windows) fail when Peer Recovery of transactions is enabled on the cluster ("Enable failover of transaction log recovery" is checked in the administrative console). . The SystemOut.log on the server side will show a client inactivity timeout: . WTRN0080W: Transaction MyEAR#MyEJB.jar#MyTest #TRANSACTIONID# has timed out due to no client activity for greater than 60 seconds. . The traces on the server side will also show an org.omg.CORBA.OBJECT_NOT_EXIST error: . org.omg.CORBA.OBJECT_NOT_EXIST: SERVANT_NOT_FOUND (4) for key #KEY# vmcid: IBM minor code: C14 completed: No at com.ibm.rmi.corba.ObjectManager.lookupServant(ObjectManager.java :110) at com.ibm.CORBA.iiop.ServerDelegate.getServant(ServerDelegate.java :312) at com.ibm.CORBA.iiop.ServerDelegate.locate(ServerDelegate.java:276 ) ... On the client side on z/OS, a transaction rollback is seen (CORBA.TRANSACTION_ROLLEDBACK): . org.omg.CORBA.TRANSACTION_ROLLEDBACK: vmcid: 0xc9c21000 minor code: 8C5 completed: No at com.ibm.ws390.tx.TransactionTerminatorImpl.commit(TransactionTer minatorImpl.java:288) at com.ibm.ws390.tx.ControllerTransactionManagerImpl.commit(Control lerTransactionManagerImpl.java:2498) ...
Local fix
The problem can be avoided if Peer Recovery is not enabled on the cluster, if only one cluster member is available, or if the request is sent to an EJB on a single application server (not clustered).
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Various issues observed in * * distributed cluster when driven by * * z/OS client. * **************************************************************** * RECOMMENDATION: * **************************************************************** Various transactional issues were observed when attempting to drive a WebSphere Application Server distributed cluster from a z/OS client application.
Problem conclusion
Address transactional issues in the environment where the failure was observed. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.25 and 8.0.0.5. 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
PM56187
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-17
Closed date
2012-04-27
Last modified date
2012-04-27
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021