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

[Olivier Thiboutot]

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

[William Bauder]

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.

-Bill



-----Original Message-----
From: omniorb-list-***@omniorb-support.com
[mailto:omniorb-list-***@omniorb-support.com] On Behalf Of Olivier
Thiboutot
Sent: Tuesday, April 01, 2008 1:19 PM
To: omniorb-***@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

[Olivier Thiboutot]

Thanks for the quick answer...

Olivier Thibout?t
D?veloppeur logiciel principal - TAO

VOXCO Canada

-----Original Message-----
From: William Bauder [mailto:***@simplified.biz]
Sent: 1 avril 2008 15:52
To: Olivier Thiboutot; omniorb-***@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.

-Bill



-----Original Message-----
From: omniorb-list-***@omniorb-support.com
[mailto:omniorb-list-***@omniorb-support.com] On Behalf Of Olivier Thiboutot
Sent: Tuesday, April 01, 2008 1:19 PM
To: omniorb-***@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

[Duncan Grisby]

Post by Olivier Thiboutot
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.

That is, as Bill guessed, the Winsock error code from WSAGetLastError(),
meaning connection reset by peer.

It will probably be very hard to track down why that's happening without
being able to turn some tracing on on the server. Have you tried running
the client with -ORBtraceLevel 30 ? Does that tell you anything that
looks relevant?

Cheers,

Duncan.