Our sysadmins fiercely denied any possibility that our problem was caused by 'their' firewall either. Accept it, come to terms with it, its just how they are.
Of course this doesn't mean you shouldn't gather all the evidence, then mercilessly crucify them for wasting your time! This, of course, is also just how _you_ are! Darren Tracey > -----Original Message----- > From: Scott Barnes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 25, 2003 11:52 AM > To: CFAussie Mailing List > Subject: [cfaussie] Re: A request exceeded the timeout. The > unresponsive > thread count is up to 1 > > > I'd open a can of bitchslap and proceed to force feed that > sysadmin its > contents :D > > Is there anyway you can dump a callstack of somekind to prove to him.. > > Scott. > > > > "Jason Barnes" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > > Ok on further investigation, it seems to be losing its > tcp/ip connection > to > > the database in mid-query. There are currently 80 > concurrent processes > > initiated from the web site which won't die. They seem to match the > > unresponsive threads. So my theory is the website makes a > connection to > the > > database, loses the connection before the database returns > its result and > on > > either side of the connection the process times out. > > > > In between the database and the website there is a > firewall. The firewall > > was changed on sunday afternoon at 2pm, the problem started > occuring at > > 10.45am monday morning. Of course the sys admins insist it is not a > firewall > > problem, even though between friday afternoon and monday > there were no > other > > changes made. > > > > > > > > "Jason Barnes" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > > > > > Has anyone experienced the following error (as appears in > server logs): > > > > > > A request exceeded the timeout. The unresponsive thread > count is up to 1 > > > > > > this count goes up to 4 before a restart....then EXACTLY > 30 minutes > later > > > (to the second) the unresponsive thread count starts again. > > > > > > We have checked logs, alerts, processes, schedules, crons > everything and > > > cannot find anything to indicate what is causing the problem. > > > > > > We are using CF4.5, on solaris 7. This has just started > today at 10.45am > > > after being fine for several months. If anyone has any > suggestions it > > would > > > be much appreciated. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to > [EMAIL PROTECTED] > > MX Downunder AsiaPac DevCon - http://mxdu.com/ > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
