[squid-users] RE: Essential ICAP service eown error not working reliably

Hi,

Just a follow up to this. Anyone know how/when squid will trigger ICAP service as down?

From ICAP logs, we can see squid is sending in an 'OPTIONS' request every second. Is this request a health-check on the ICAP service? Or is there any other function to it?

We're still seeing very long pauses in our ICAP server that should really trigger an ICAP error on squid, but it isn't always.

Thanks,
Justin

-----Original Message-----
From: Justin Lawler
Sent: Tuesday, October 11, 2011 4:29 PM
To: squid-users_at_squid-cache.org
Subject: [squid-users] Essential ICAP service eown error not working reliably

Hi,

We have an application that integrates with squid over ICAP - a java based application. We're finding that the java application has very long garbage collection pauses at times (20+ seconds), where the application becomes completely unresponsive.

We have squid configured to use this application as an essential service, with a timeout for 20 seconds. If the application goes into a GC pause, squid can throw an 'essential ICAP service is down' error.

The problem is most of the time it doesn't. It only happens maybe 20% of the time - even though some of the pauses are 25 seconds+.

Squid is setup to do an 'OPTIONS' request on the java application every second, so I don't understand why it doesn't detect the java application becoming unresponsive.

Any feedback much appreciated.

Thanks,
Justin
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
Received on Tue Oct 18 2011 - 05:02:32 MDT