[omniORB] giopstream::CommFailure

João Lopes jc.lopes at gmail.com
Thu Jun 28 15:58:55 BST 2007


AFAIK you have to restart the client ORB every time the server dies.
The reason for this is that the client make a TCP connection to the
server and when the server comes up again it cannot recover the old
TCP connection from the client.

Please correct me if I'm wrong.

João Lopes



On 6/28/07, Tahar Ouhrouche <tahar.ouhrouche at gmail.com> wrote:
> Hi All,
> I have a client/server application using omniORB4.
> When I run the client, everything goes well. But when I stop the server then
> I get this message in debug mode:
>
> omniORB: throw giopStream::CommFailure from
> giopStream.cc:874(0,NO,COMM_FAILURE_UnMarshalArguments)
>  omniORB: Server connection refcount = 1
>  omniORB: Server connection refcount = 0
> omniORB: Server close connection from giop:tcp: 134.32.185.82:1724
> omniORB: AsyncInvoker: thread id = 4 has exited. Total threads = 3
>
> The client does not crash. it works fine. I try to run the server a second
> time (without restarting the client) then I get an exception which causes a
> crash to the client.
>
>  omniORB: throw giopStream::CommFailure from
> giopStream.cc:874(0,NO,COMM_FAILURE_UnMarshalArguments)
>  omniORB: Server connection refcount = 1
>  omniORB: Server connection refcount = 0
> omniORB: Server close connection from giop:tcp: 134.32.185.82:1736
> omniORB: AsyncInvoker: thread id = 5 has exited. Total threads = 3
>
> Do I need to restart the client every time the server goes down?
>
> Thanks a lot for your help,
>
> Cheers,
>
> Tahar Ouhrouche
> Software engineer,
> Schlumberger - Oslo
>
>
>
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>
>


More information about the omniORB-list mailing list