RE: bugs/problems with Orbacus 4.2.2

> -----Original Message-----
> From: Darren Middleman [mailto:[email protected]]
> Sent: Friday, April 15, 2005 6:29 PM
> To: Andrey Mikhalchuk
> Cc: [email protected]; 'Packet411 Corporation'
> Subject: Re: [OB-Users] bugs/problems with Orbacus 4.2.2
> 
> Hi Andrey,
> 
> > Right, we'have switched the entire company development to JDK 1.5. After
> > that switching Orbacus won't compile by default, so our build engineer
> > modified the makefiles according to the installation instructions
> included
> > with the patch package. The changes he made are exactly the ones you
> > mentioned in your answer. This helped and we got Orbacus compiled as
> well as
> > all our code.
> >
> > Unfortunately during runtime I'm still getting those "method not found"
> > exceptions and using "-Xbootclasspath" doesn't help.
> >
> > Do you have any positive experience of running Orbacus 4.2.2 with
> JDK1.5? Is
> > this configuration welcomed by IONA or it would be better to switch back
> to
> > 4.2.1 and JDK1.4.2?
> >
> > [...]
> >
> > It's difficult to provide concrete details, because entire behavior of
> > eventserv and nameserv seems "strange" in many aspects. In particular:
> > - sometimes nameserv and eventserv just crash without any visible
> reason.
> > What do I mean here is that we saw several situations on our server when
> > those servers start and even if they experience no load at all (the
> modules
> > didn't start yet) they shut down (process just dissapears)
> > - in some situations eventserv start loosing too many events. Too many
> means
> > more then 20% on very low load, like 10 events sent with 1event/sec rate
> > - if a process that registers with nameserv goes down and then start
> again
> > it might improperly be rebinded in nameserv. This happens in
> approximately
> > 50% of all module restarts. It stays registered, but when another module
> > tries to make call to one of methods it provides both crash with non-
> Corba
> > exception. Restarting nameserv solves the problem.
> >
> > Such situations were not noticed in Orbacus 4.2.1 and JDK1.4.2.
> >
> > [...]
> 
> As a follow-up to my previous email, could you also let me know what
> compiler you are using to build the nameserv and eventserv C++
> applications
> (assuming you are using the C++ executables).

We're using gcc 3.4.2. The tests run on dual-Opteron Solaris 9 Sun box. Java
code is compiled and run with ant 1.6.2 - probably there are issues with one
of those environment options.

BTW, we recompiled 4.2.2 with JDK 1.4.2 and those ugly exceptions on startup
disappeared. After further investigation I can say that the issue of
component "strange" rebind only happens when client code is written in C++
and server code is in Java. 

Thanks!
Andrey.

> 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