PM06930: ORG.OMG.CORBA.BAD_OPERATION: VMCID:0XC9C25000 MINOR CODE:757 COMPLETED: MAYBE

Fixes are available

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM06930: ORG.OMG.CORBA.BAD_OPERATION: VMCID:0XC9C25000 MINOR CODE:757 COMPLETED: MAYBE

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

R700 PSY UK57722

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

Share your feedback

Need support?