[omniORB] Issues with persistent objects

[Martin B.]

Hmmm ... it seems to me that the client side never notices that the 
server goes offline (which does seem a bit odd, I would have thought 
that the server closes the connection when you restart it, which should 
be apparent in the client log).

If the client never notices that the server goes offline, it's original 
TCP connection on 4001 will certainly be invalid by the time the server 
has restarted. (Or will it? I'm never too sure with those sockets :-)

You say you restart the server. An interesting bit of logging would be 
if there's any trace of the server shutdown in the client logs. That is: 
just shutdown the server, and then compare the loggings (with 
timestamps) of the server and the client at and after server shutdown.

cheers,
Martin

ps: You might have noticed I'm not the biggest expert in this. Just 
learning as much as you do I'd say. :-)


On 01.02.2011 05:12, anirudh nair wrote:
>  > Analysis will be easier when you add traceException=1
>
> Client trace with traceException=1
>
> omniORB: (0) 2011-02-01 09:19:56.896000: Invoke '_is_a' on remote:
> key<Param>
> omniORB: (0) 2011-02-01 09:19:56.898000: Client attempt to connect to
> giop:tcp:1
> 0.9.18.193:4001 <http://0.9.18.193:4001>
> omniORB: (1) 2011-02-01 09:19:56.898000: AsyncInvoker: thread id = 1 has
> started
> . Total threads = 1
> omniORB: (1) 2011-02-01 09:19:56.899000: Scavenger task execute.
> omniORB: (0) 2011-02-01 09:19:56.908000: Client opened connection to
> giop:tcp:10
> .9.18.193:4001
> omniORB: (0) 2011-02-01 09:19:56.909000: sendChunk: to
> giop:tcp:10.9.18.193:4001 <http://10.9.18.193:4001>
>   80 bytes
> omniORB: (0) 2011-02-01 09:19:56.911000: inputMessage: from
> giop:tcp:10.9.18.193
> :4001 25 bytes
> omniORB: (0) 2011-02-01 09:19:56.911000: Return '_is_a' on remote:
> key<Param>
> omniORB: (0) 2011-02-01 09:19:56.913000: Creating ref to remote: key<Param>
>   target id      : IDL:Param/ParamBook:1.0
>   most derived id:
> omniORB: (0) 2011-02-01 09:19:56.914000: ObjRef() -- deleted.
> omniORB: (0) 2011-02-01 09:20:10.519000: Invoke 'send_book' on remote:
> key<Param
>>
> omniORB: (0) 2011-02-01 09:20:10.520000: sendChunk: to
> giop:tcp:10.9.18.193:4001 <http://10.9.18.193:4001>
>   3249 bytes
> omniORB: (0) 2011-02-01 09:20:10.522000: inputMessage: from
> giop:tcp:10.9.18.193
> :4001 25 bytes
> omniORB: (0) 2011-02-01 09:20:10.522000: Return 'send_book' on remote:
> key<Param
>>
>
> // first call after server restart
>
> omniORB: (0) 2011-02-01 09:21:07.904000: Invoke 'send_book' on remote:
> key<Param
>>
> omniORB: (0) 2011-02-01 09:21:07.905000: sendChunk: to
> giop:tcp:10.9.18.193:4001 <http://10.9.18.193:4001>
>   3249 bytes
> omniORB: (0) 2011-02-01 09:21:07.906000: Error in network receive (start
> of mess
> age): giop:tcp:10.9.18.193:4001 <http://10.9.18.193:4001>
> omniORB: (0) 2011-02-01 09:21:07.907000: throw giopStream::CommFailure
> from giop
> Stream.cc:874(0,MAYBE,COMM_FAILURE_WaitingForReply)
> omniORB: (0) 2011-02-01 09:21:07.912000: Client connection refcount = 0
> omniORB: (0) 2011-02-01 09:21:07.913000: Client close connection to
> giop:tcp:10.
> 9.18.193:4001
> omniORB: (0) 2011-02-01 09:21:07.916000: throw COMM_FAILURE from
> omniObjRef.cc:7
> 84 (MAYBE,COMM_FAILURE_WaitingForReply)
>
> // second call after server restart: No exception trrown here. Works
> perfectly
> omniORB: (0) 2011-02-01 09:21:07.926000: Invoke 'send_book' on remote:
> key<Param
>>
> omniORB: (0) 2011-02-01 09:21:07.928000: Client attempt to connect to
> giop:tcp:1
> 0.9.18.193:4001 <http://0.9.18.193:4001>
> omniORB: (0) 2011-02-01 09:21:07.940000: Client opened connection to
> giop:tcp:10
> .9.18.193:4001
> omniORB: (0) 2011-02-01 09:21:07.940000: sendChunk: to
> giop:tcp:10.9.18.193:4001 <http://10.9.18.193:4001>
>   3249 bytes
> omniORB: (0) 2011-02-01 09:21:07.945000: inputMessage: from
> giop:tcp:10.9.18.193
> :4001 25 bytes
> omniORB: (0) 2011-02-01 09:21:07.946000: Return 'send_book' on remote:
> key<Param
>>
>
> Thanks
> Anirudh
>
>
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list