[omniORB] occasional Exception "giopStream::CommFailure from giopStream.cc:878(0,MAYBE,COMM_FAILURE_WaitingForReply)"

[Isaac]

Hello, Peter:

Thanks for replying.

I guess this might be some network problem between my client machine and
server machine.
cause the same program works well in my another client machine.

I can reproduce it reliably, but I don't know how to follow the network
problem, get tcpdump trace or sth. like that?

thanks


On Sat, Oct 10, 2009 at 3:56 PM, Peter Klotz <peter.klotz at aon.at> wrote:

> Hello Isaac
>
>  my client will occasionally throw this exception:
>>
>> 2009-10-10 10:14:35,389 [0xb61d4b90] - Start to open session ...
>>
>> omniORB: Creating ref to remote: key<NameService>
>>  target id      : IDL:omg.org/CORBA/Object:1.0 <
>> http://omg.org/CORBA/Object:1.0>
>>  most derived id:
>> omniORB: sendChunk: to giop:tcp:172.29.1.3:12348 <http://172.29.1.3:12348>
>> 100 bytes
>> omniORB:
>> 4749 4f50 0100 0100 5800 0000 0000 0000 GIOP....X.......
>> 0400 0000 0120 2020 0b00 0000 4e61 6d65 .....   ....Name
>> 5365 7276 6963 6520 0600 0000 5f69 735f Service ...._is_
>> 6100 2020 0000 0000 2800 0000 4944 4c3a a.  ....(...IDL:
>> 6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin <
>> http://omg.org/CosNamin>
>> 672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
>> 312e 3000                               1.0.
>> omniORB: Error in network receive (start of message): giop:tcp:
>> 172.29.1.3:12348 <http://172.29.1.3:12348>
>> omniORB: throw giopStream::CommFailure from
>> giopStream.cc:878(0,MAYBE,COMM_FAILURE_WaitingForReply)
>> omniORB: Client connection refcount = 0
>> omniORB: Client close connection to giop:tcp:172.29.1.3:12348 <
>> http://172.29.1.3:12348>
>> omniORB: throw COMM_FAILURE from omniObjRef.cc:808
>> (MAYBE,COMM_FAILURE_WaitingForReply)
>> omniORB: omniRemoteIdentity deleted.
>> omniORB: ObjRef() -- deleted.
>>
>> 2009-10-10 10:14:35,390 [0xb61d4b90] - Cann't open the session!
>>
>> the network between client and server seems no problem (ping and it's
>> alive)
>> can someone give me some clues to locate the problem?
>>
>
> I am seeing the same problem after upgrading to omniORB 4.1.4. It never
> occurred in 4.1.3.
>
> It happens sporadically so I have no test case that can reproduce it
> reliably.
>
> If it is something introduced between 4.1.3 and 4.1.4 looking at the
> differences should give a hint. I tried this once but there were a lot of
> license changes, so you have to deal with a lot of "noise".
>
> Regards, Peter.
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>



-- 
Best Regards,
Isaac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20091010/0a8e4ab4/attachment.htm