[omniORB] Nested Calls?

[Kevin Wooten]

Just a boneheaded move! I was running the client code in a seperate =
thread, so I could just call orb::run from the main thread....but forgot =
to call orb::run...that was all!=20

Sorry to bother

>> -----Original Message-----
>> From: bjorn rohde jensen [mailto:shamus@tdcadsl.dk]
>> Sent: Tuesday, March 12, 2002 5:17 AM
>> To: omniorb-list@uk.research.att.com
>> Subject: Re: [omniORB] Nested Calls?
>>=20
>>=20
>> Hi Kevin,
>>=20
>>  There are several parameters in omniORB's configuration=20
>> file affecting
>> the connection
>> management. You could try to set the connection timeout to something
>> reasonable and
>> set the orb trace level fairly high. You should see a timeout error,
>> which might be
>> enlightening, in the trace. There are also parameters limiting the
>> number of concurrent
>> invocations from a client, maybe you have used them all?
>>=20
>> Yours sincerely,
>>=20
>> bjorn
>>=20
>> Kevin Wooten wrote:
>> >=20
>> > If I am using the default POA and omniORB4 on both client=20
>> and server, what is stopping nested calls from working? My=20
>> server is trying to call back to the client, and it=20
>> deadlocks. I am sure it is something simple I am missing,=20
>> but I cannot seem to find the answer in the docs or the archives.
>> >=20
>> > TIA,
>> >=20
>> > Kevin Wooten
>> > iTRACS Corporation
>> > email: kwooten@itracs.com
>> > phone: 480-557-8000 ext. 132
>> >
>>=20
>>=20