[omniORB] OmniOrb terminates after CommFailure

[Waddell, Steve]

OmniOrb seems to throw an exception and then terminate. I am sporactically getting
There errors:

"omniORB: throw giopStream::CommFailure from giopStream.cc:1084(0,NO,TRANSIENT_ConnectFailed)
terminate called after throwing an instance of 'omni::giopStream::CommFailure' "

sometimes this is preceded by _non_existent calls:

"omniORB: Invoke '_non_existent' on remote: key<.PMC.........POA.pdp........PDP.Main.Manager.pdp.PDP.Main.Manager>
omniORB: throw giopStream::CommFailure from giopStream.cc:1084(0,NO,TRANSIENT_ConnectFailed)
terminate called after throwing an instance of 'omni::giopStream::CommFailure' "

And other times it is preceded by "switch rope":

"omniORB: Client attempt to connect to giop:tcp:192.4.124.19:40020
omniORB: Switch rope to use address giop:tcp:192.4.124.19:40020
omniORB: throw giopStream::CommFailure from giopStream.cc:1084(0,NO,TRANSIENT_ConnectFailed)"

Should not all exceptions be handled and then passed on to the application? But in this case the process
goes through line 1084 of giopStream.cc and then on to termination. What could be happening here?

I am on OmniOrb 4.0.6 on redhat update 6 (we have also seen it on redhat update 4)

Thanks for any help

Steve Waddell


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20090218/25eee037/attachment.htm