[omniORB] COMM_FAILURE Exception

[Jaskirat Singh]

Hello,



I have a server application running on omniORB version 4.0.7 and the
clients are written using omniORB version 4.0.1.

When clients try to connect to the server the client gets the
COMM_FAILURE exception.



On further analysis whenever client makes the IDL call the COMM_FAILURE
exception is caught at the client side.



Earlier the server and client were both on omniORB version 4.0.1 and it
used to work perfectly.



Is there any known issue on this?



Any help on this will be very much appreciated.



Thanks,



JASKIRAT SINGH



Phone: [phone]



CONFIDENTIALITY NOTICE
This e-mail transmission and any documents, files, or previous e-mail
messages appended or attached to it, may contain information that is
confidential or legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that you must not read this
transmission and that any disclosure, copying, printing, distribution,
or use of the information contained or attached to this transmission is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender by telephone [phone] or return
e-mail message ***@quark.com and delete the original transmission,
its attachments, and any copies without reading or saving in any manner.
Thank you.



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

[Jaskirat Singh]

In addition to this I have also found the minor code when this
communication failure occurs.



The minor code associated with this is COMM_FAILURE_WaitingForReply.



Any information will be very much appreciated.



Thanks,

Jaskirat



________________________________

From: omniorb-list-***@omniorb-support.com
[mailto:omniorb-list-***@omniorb-support.com] On Behalf Of Jaskirat
Singh
Sent: Tuesday, April 03, 2007 6:57 PM
To: omniorb-***@omniorb-support.com
Cc: Duncan Grisby
Subject: [omniORB] COMM_FAILURE Exception



Hello,



I have a server application running on omniORB version 4.0.7 and the
clients are written using omniORB version 4.0.1.

When clients try to connect to the server the client gets the
COMM_FAILURE exception.



On further analysis whenever client makes the IDL call the COMM_FAILURE
exception is caught at the client side.



Earlier the server and client were both on omniORB version 4.0.1 and it
used to work perfectly.



Is there any known issue on this?



Any help on this will be very much appreciated.



Thanks,



JASKIRAT SINGH



Phone: [phone]



CONFIDENTIALITY NOTICE
This e-mail transmission and any documents, files, or previous e-mail
messages appended or attached to it, may contain information that is
confidential or legally privileged. If you are not the intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that you must not read this
transmission and that any disclosure, copying, printing, distribution,
or use of the information contained or attached to this transmission is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender by telephone [phone] or return
e-mail message ***@quark.com and delete the original transmission,
its attachments, and any copies without reading or saving in any manner.
Thank you.



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

[Duncan Grisby]

Post by Jaskirat Singh
I have a server application running on omniORB version 4.0.7 and the
clients are written using omniORB version 4.0.1.
When clients try to connect to the server the client gets the
COMM_FAILURE exception.
On further analysis whenever client makes the IDL call the COMM_FAILURE
exception is caught at the client side.

Get traces from both sides using -ORBtraceLevel 25 -ORBtraceInvocations 1.

Cheers,

Duncan.