[omniORB] omniORB 4.0 problems

Ivanov, Roumen Roumen.Ivanov@drkw.com
Fri, 19 Oct 2001 12:24:05 +0200


Just to close the thread.
It turned so that I went back to my initial state - on my machine it works
normally and on the test machine of my colleagues - not.
I finally realized, that they recently added a command line parameter
-ORBclientCallTimeout 10. They thought these are seconds, but it is
milliseconds and guess what happens. After compiling with omniORB4 it
stopped working because the call takes a little bit more. Sometimes it even
succeeds just to make the things worse.
It was a painful way to the truth and the moral is simply "Be more
concentrated". I had all the information.

Thanks again, you are doing great job there,
Roumen


-----Original Message-----
From:	Ivanov, Roumen [SMTP:Roumen.Ivanov@drkw.com]
Sent:	Thursday, October 18, 2001 15:31
To:	'omniorb list'
Subject:	RE: [omniORB] omniORB 4.0 problems 

Sorry, I see, I mistyped it. Sorry for the noise
Thanks a lot, 
Roumen 



-----Original Message-----
From:	Duncan Grisby [SMTP:dgrisby@uk.research.att.com]
Sent:	Thursday, October 18, 2001 15:09
To:	Ivanov, Roumen
Subject:	Re: [omniORB] omniORB 4.0 problems 

On Thursday 18 October, "Ivanov, Roumen" wrote:

> I have -ORBInitRef NameService=corbaname::hostname . Should be enough
> shouldn't it? I don't have any registry, environment or config file
entries.
> I attached a file with ORBtraceLevel 30. Ith shows Distribution date: Wed
> Oct 17 19:47:21 BST 2001 dpg1. Don't know why.

It should be enough, but note below...

> swgalsrv -ORBInitRef NameSrvice=corbaname::rum1 -ORBtraceLevel 30
[...]
> omniORB:   InitRef = NameSrvice=corbaname::rum1

You've spelled NameService wrong. That might not have been the problem
before, but it's definitely a problem now.

Cheers,

Duncan.

-- 
 -- Duncan Grisby  \  Research Engineer  --
  -- AT&T Laboratories Cambridge          --
   -- http://www.uk.research.att.com/~dpg1 --


If you have received this e-mail in error or wish to read our e-mail
disclaimer statement and monitoring policy, please refer to
http://www.drkw.com/disc/email/ or contact the sender.