[omniORB] omniORB and Java 1.3...
Thomas Zumbiehl
zumbiehl@bvassociates.fr
Mon Jul 15 11:20:05 2002
Well, I'm not sure that it comes from a DNS problem. In fact, the method is
called on an interface which (CORBA) reference is passed through a method of
the server (like a registerListener()).
This problem happens only once during the client lifecycle. It's only the
very fist time the server should contact the client. This type of problem
does not occur when this mecanism is used between two applications using
omniORB. That makes me think that the problem may come from the java 1.3
embedded ORB.
Bye
Thomas
-----Message d'origine-----
De : dpg1@grisby.org [mailto:dpg1@grisby.org]De la part de Duncan Grisby
Envoyé : lundi 15 juillet 2002 12:02
À : Thomas Zumbiehl
Cc : OmniORB List (E-mail)
Objet : Re: [omniORB] omniORB and Java 1.3...
On Thursday 11 July, "Thomas Zumbiehl" wrote:
> The very first time the server has to contact the client (either by
calling
> a method defined in the IDL, or by calling the _remote_non_existent()
method
> of omniObjRef), it takes a very long time to complete (from 5 to 10 s), as
> if the two ORB have difficulties to establish communication.
There's probably something broken about your DNS naming setup, meaning
the host lookup times out before a second attempt succeeds.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan@grisby.org --
-- http://www.grisby.org --