Skip to main content

IBM JDK 1.3.1 CORBA.BAD_INV_ORDER exception

  • February 16, 2013
  • 0 replies
  • 1 view

Problem:

  • Product Name: VisiBroker for Java
  • Product Version: 4.x, 5.x, and 6.x
  • Product Component: Core
  • Platform/OS Version: AIX
  • JDK Version: IBM JDK 1.3.1 SR 5(ca131-20030630)


This article address one known cause of the CORBA.BAD_INV_ORDER exception that occurs under IBM JDK 1.3.1 only. The error is commonly seen during the start up and activation of a CORBA servant, but may occur when accessing remote object references as a client as well.

A CORBA application running under IBM AIX JDK 1.3.1 SR 5(ca131-20030630 )may throw the following exception:

org.omg.CORBA.BAD_INV_ORDER: The Servant has not been associated with an ORBinstance                  minor code: 0                   completed: No

 

Resolution:

This is a known issue with this JDK release and is documented by IBM in the following article:CORBA Error while booting ICS
 
To work around this issue:

  • Download and install the latest JDK 1.3.1 patch recommended by IBM.
  • Use the VM param -Dcom.ibm.CORBA.POACompatibilityMode=true.

This parameter would be required for any CORBA application using the VisiBroker for Java ORB runtime.

 

#VisiBroker
#Security