Package: libomniorb4
Version: 4.0.5-1
Severity: grave
Tags: patch
In case of setting serverCallTimeOutPeriod in /etc/omniORB4.cfg
or by command line, omniORB does not honour the timeout which
leads to inaccessibility of any server application, if too many
client connections are not closed by the client side.
The patch is by Duncan Grisby (omniORB upstream) and will
be included in CVS and upcoming 4.0.6, I hope.
diff -u -r1.1.4.21 giopStrand.cc
--- src/lib/omniORB/orbcore/giopStrand.cc 17 Oct 2004 21:48:40 -0000 1.1.4.21
+++ src/lib/omniORB/orbcore/giopStrand.cc 16 Mar 2005 09:15:29 -0000
@@ -540,10 +540,12 @@
giop_s->giopStreamList::insert(servers);
}
- if (remove && giop_s->state() != IOP_S::WaitingForReply)
- delete giop_s;
- else
- restart_idle = 0;
+ if (remove) {
+ if (giop_s->state() != IOP_S::WaitingForReply)
+ delete giop_s;
+ else
+ restart_idle = 0;
+ }
if (restart_idle && !biDir) {
CORBA::Boolean success = startIdleCounter();
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
