Skip to Main Content

Java APIs

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

CORBA COMM FAILURE AND ORB

843793Oct 31 2001 — edited Nov 9 2001
We are currently experiencing numerious and periodic CORBA COMM FAILUREs in prd. We are utilizing JDK 1.3 / CORBA and trying to submit to a C++ server object. When the web server starts up, it initializes the ORB using the ior and orb.init(). When the actual calls are made, we are narrowing to the server object and making the call. Problem is that periodically we get the CORBA COMM FAILURE when we make the call. During our investigation, we determined that the actual servers look to be running just fine and they are registared with the naming service. When this error occurs, we present the user with a communication failure message.

Our theory is that the ORB is caching the server objects and their connection paths. If the connection is broken for whatever reason, it throws a CORBA COMM FAILURE instead of trying to reconnect to the server object. Can anyone verify our theory? A detailed understanding of how the java ORB works would be very helpful.

Secondly, what is the best way to handle this exception. Should we shutdown the ORB and restart it? I am very apprehensive about this since users running on the other threads will be affected. Anyone familiar with orb.disconnect(Object ob) or orb.connect(Object ob)? Should I do these steps in my exception handling block to get the ORB to set up or cache a real server object?

In reading another discussion thread, I ran across someone using the objRef._non_existent() to get it to go. Anyone familiar with this method and understand the implications of its use?

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Dec 7 2001
Added on Oct 31 2001
1 comment
664 views