[omniORB] COMM_FAILURE and minor code (Omni ORB 2.80)

Olivier Thiboutot Olivier.Thiboutot at voxco.com
Tue Apr 1 17:02:39 BST 2008

Thanks for the quick answer...

Olivier Thiboutôt
Développeur logiciel principal - TAO

VOXCO Canada

-----Original Message-----
From: William Bauder [mailto:bill at simplified.biz] 
Sent: 1 avril 2008 15:52
To: Olivier Thiboutot; omniorb-list at omniorb-support.com
Subject: RE: [omniORB] COMM_FAILURE and minor code (Omni ORB 2.80)

This is just a guess, but it looks like the minor code is the underlying winsock error code - 10054 is WSAECONNRESET (connection reset by peer) - which would be the server deliberately closing the socket.


-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Olivier Thiboutot
Sent: Tuesday, April 01, 2008 1:19 PM
To: omniorb-list at omniorb-support.com
Subject: [omniORB] COMM_FAILURE and minor code (Omni ORB 2.80)

Hi Duncan and all others...

Lets get into the past !

In using OmniOrb 2.80 (very stable... Btw) and we meet, at client production site, one simple error! COMM_FAILURE... I cannot put a real problem on this cause around that time (got a time stamp on client side), the server was running fine. I can look at more than 50 calls going right around that time (250 ms around). I've got 50 thread in the server pool.

Here is my problem. The execution delay to catch the COMM_FILURE is around 115(ms). The Question. I've got a minor code = 10054 and cannot rely on anything into Omni. Can you please help me where to look to have those codes intepretation.

System : Windows 2003 server
Compiler : MVC++ 6.0
Omni : 2.80

I cannot put the trace output on the production site and that error is time to time.

Best regards

Olivier Thiboutôt
Développeur logiciel principal - TAO

VOXCO Canada

omniORB-list mailing list
omniORB-list at omniorb-support.com

More information about the omniORB-list mailing list