home / blog

Jacorb 2.2.4 NamingService broken

The naming service jacorb appears to be broken in release 2.2.4. This is only really a problem if you’re working on a legacy project where you can’t use a more recent version.

It allows clients to connect, but causes them to throw the following exception when trying to resolve a name.

org.omg.CORBA.BAD_INV_ORDER: Server-side Exception: The Servant
has not been associated with an ORB instance  vmcid: 0x0  minor code: 0
completed: No 
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
        at java.lang.reflect.Constructor.newInstance(Unknown Source)
        at org.jacorb.orb.SystemExceptionHelper.read(SystemExceptionHelper.java:173)
        at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:326)
        at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:967)
        at org.jacorb.orb.Delegate.invoke(Delegate.java:868)
        at org.jacorb.orb.Delegate.is_a(Delegate.java:1268)
        at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:49)
        at org.omg.CosNaming.NamingContextExtHelper.narrow(NamingContextExtHelper.java:57)
        at com.example.horse.ServerTestImpl.resolve(Unknown Source) 
This entry was posted in geek and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published.