Fixes are available
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Running WebSphere Application Server on zOS, in some cases a RMI/IIOP call for an EJB on the server causes the below exception. CORBA BAD_OPERATION 0xc9c25757 Maybe; nested exception is: org.omg.CORBA.BAD_OPERATION: vmcid: 0xc9c25000 minor code: 757 completed: Maybe] java.rmi.RemoteException | servername STCnumber | ejbname| UNKNOWN EXCEPTION LEVEL | ROOTEXCEPTION | CORBA BAD_OPERATION 0xc9c25757 Maybe; nested exception is: org.omg.CORBA.BAD_OPERATION: vmcid: 0xc9c25000 minor code:757 completed: Maybe | Caused by: org.omg.CORBA.BAD_OPERATION: vmcid: 0xc9c25000 minor code: 757 completed: Maybe at java.lang.J9VMInternals.newInstanceImpl(Native Method) at java.lang.Class.newInstance(Class.java:1325) at com.ibm.rmi.util.Utility.readSystemException(Utility.java:1 at com.ibm.rmi.iiop.CDRReader.readSystemException(CDRReader.ja at com.ibm.ws390.orb.ClientDelegate.commonInvoke(ClientDelegat at com.ibm.ws390.orb.ClientDelegate.invoke(ClientDelegate.java at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:4 The same RMI/IIOP call on distributed WSAS results with 'completed: NO' as shown below. org.omg.CORBA.BAD_OPERATION: SERVER (id=xxxxxxxx, host=aaa.bbb.ccc) TRACE START: org.omg.CORBA.BAD_OPERATION: vmcid:0x0 minor code: 0 completed: No at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandl at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDele at com.ibm.rmi.iiop.ORB.process(ORB.java:513) at com.ibm.CORBA.iiop.ORB.process(ORB.java:1574) at com.ibm.rmi.iiop.Connection.respondTo(Connection.java at com.ibm.rmi.iiop.Connection.doWork(Connection.java:27 at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.jav at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java: at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java SERVER (id=xxxxxxxx, host=aaa.bbb.ccc) TRACE END. vmcid: 0x0 minor code: 0 completed: No at sun.reflect.NativeConstructorAccessorImpl.newInstance0 at sun.reflect.NativeConstructorAccessorImpl.newInstance( at sun.reflect.DelegatingConstructorAccessorImpl.newInsta at java.lang.reflect.Constructor.newInstance(Constructor. at com.ibm.rmi.iiop.ReplyMessage._getSystemException(Repl at com.ibm.rmi.iiop.ReplyMessage.getSystemException(Reply at com.ibm.rmi.iiop.ClientResponseImpl.getSystemException at com.ibm.rmi.corba.ClientDelegate.intercept(ClientDeleg at com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegat at com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate at com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegat at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.j The purpose of this apar is to make the behavior on WSAS on zOS same as distributed WSAS where the error will report 'completed: No' instead of 'completed: Maybe'
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application Server * V7.0 * **************************************************************** * PROBLEM DESCRIPTION: Incorrect COMPLETED_MAYBE Completion * * Status was set for an * * org.omg.CORBA.BAD_OPERATION * * SystemException. * **************************************************************** * RECOMMENDATION: * **************************************************************** A CompletionStatus of COMPLETED_MAYBE was returned for a CORBA BAD_OPERATION. The native code which drives the dispatch method for RMI/IIOP requests sets indicators into a native object to represent that state of dispatch. This state overrides any CompletionStatus determined under the dispatch code. In this case it assumed that since a successful completion of the dispatch method had not occurred that the CompletionStatus must be set to MAYBE.
Problem conclusion
Updated the native state around the RMI/IIOP dispatch method to honor the CompletionStatus determined within the dispatch method. APAR PM06930 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.11 of WebSphere Application Server V7.0 Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM06930
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-05
Closed date
2010-03-12
Last modified date
2010-07-02
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK57722
UP10/06/17 P F006
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
25 October 2021