Re: [openorb-users] silly writeLock error in namingservice

[Michael R. <mi...@ru...>]

> Dear Fellow Users,

Hi Bill,

> This error seems so silly.  I copied all
> my files (openorb, naming service, etc, to
> another computer running Mac OS 10.1.2, with
> the same directory structure and now there
> is an error when trying to run the naming
> service.
>
> Command line in script
> ${JAVA_HOME}/bin/java  org.openorb.ins.Server  -ORBPort=5001 -verbose $*
>
> result:
>
> Exception in thread "main" org.omg.CORBA.COMM_FAILURE:   minor code:
> 1398079490  completed: No
>          at
>
com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:
914)

When you look at the classes from the stack trace:
"com.sun.corba.se.internal". This always indicates that the wrong ORB is
used. Here the Sun JDK ORB classes are instantiated and not the OpenORB
classes. You forgot to specify OpenORB at your command line with the
parameters:

-Dorg.omg.CORBA.ORBClass=org.openorb.CORBA.ORB
-Dorg.omg.CORBA.ORBSingletonClass=org.openorb.CORBA.ORBSingleton

or you have forgotten to move the orb.properties file (from user.home
folder) as well, because you can also put the two properties for system wide
settings there...

Hope this helps,
   Michael