Re: bugs/problems with Orbacus 4.2.2

Hi Andrey,

> I have recently updated to Orbacus 4.2 Patch 2 from 4.2.1 and found a
> few possible bugs in Orbacus 4.2.2 which seem to make the Orbacus
> system work improperly:
> 
> 1.        Now with 4.2.2, on every ORB start I'm getting a lot of
> exceptions like
> 
>      [java] Exception in thread "Thread-2" java.lang.NoSuchMethodError:
> org.omg.PortableInterceptor.IORInterceptor_3_0.adapter_manager_state_changed
> (Ljava/lang/String;S)V
> 
>      [java]     at
> com.ooc.OB.PIManager.adapterManagerStateChange(PIManager.java:688)
> 
>      [java]     at
> com.ooc.OBPortableServer.POAManager_impl.activate(POAManager_impl.java:220)
> 
>      [java]     at com.packet411.framework.application.OrbRunner.run(Unknown
> Source)
> 
>      [java]     at java.lang.Thread.run(Thread.java:595)
> 
> After printing those exceptions, my program continue to operate in
> normal way. I have checked the Orbacus 4.2.2 source code and found
> that the method adapter_manager_state_changed implementation is really
> seems to be just missing in the Service Pack 2 patch source code. My
> same code works fine with Orbacus 4.2.1 because the source code of
> 4.2.1 doesn't contain calls to that missing
> adapter_manager_state_changed method.
> 

Are you using Java 1.4 or 1.5?  This looks like the usual error associated 
with using newer JDKs with Orbacus.  You should make sure that you uncomment 
the BOOTCLASSPATH option in the config/Make.rules (Unix) or
config\Make.rules.make (Windows) file when building Orbacus.  You should
also use the option '-Xbootclasspath/p:$CLASSPATH' (or 
'-Xbootclasspath/p:%CLASSPATH%' for Windows) when running your applications.  
For example:

  java -Xbootclasspath/p:$CLASSPATH hello.Server


> 2.        My other problem is with nameserv. I'm starting a mix of 4
> processes, all making calls to each other and sending events for
> Orbacus event service. The second start of the system causes incorrect
> binding -- a C++ component process becomes invisible to the other
> processes. After nameserv and eventserv are restarted everything work
> fine again. This happens only from time to time (20-40% of all runs,
> depending on the phase of the Moon). I'm always using rebind for
> services registration, but it seems that in some situations Orbacus
> 4.2.2 binds services incorrectly. This problem also was not noticed in
> 4.2.1.

Can you give me a bit more information on what you are seeing here?  How
are you starting these process and binding them with the naming service?  I
don't believe anything changed between the 4.2.1 and 4.2.2 with regards to
the name service so I'm not sure what could be causing the problems you are
seeing.  Any other information you could provide here would be helpful.

Regards,
Darren

-- 
Darren Middleman, Software Engineer
Team Orbacus - Your CORBA Source
Email: mailto:[email protected]
WWW: http://www.orbacus.com/
_______________________________________________
OB-Users Mailing List - [email protected]
http://mail.ooc.nf.ca/mailman/listinfo/ob-users
Visit our support FAQ before you send a message.
http://www.orbacus.com/faq/support.html