This document was generated from CDN thread
Created by: null on 01-12-2005 06:44:07 PM
Sometimes, during the middle of the call, we are getting 503 errors returned from the Tomcat server running Audium Call Services. That is causing the voice browser to through an error which is returning the "Due to technical difficulties we cannot service your call, please call back later" default error message in Audium.
Since are using 3.4.2 Call Services (yes, the non-GA released one that fixed one of our problems), you are going to suggest that we upgrade, but I was wondering if there were any known situations where we might encounter random 503 errors during the middle of the call.
Subject: RE: 503 Service Unavailable
Replied by: Michael Bochynski on 01-12-2005 07:24:58 PM
Hi Kitson,
Yes, we strongly encourage you to migrate to Audium Call Services 3.4.3 release.
However, error 503, in most cases, is sent when there is a network latency and/or server is overloaded. Do you see any pattern in those 503 errors? Does it happen in your custom code or accessing third party services?
Regards,
Michael
Subject: Random 503...
Replied by: null on 01-12-2005 08:00:56 PM
However, error 503, in most cases, is sent when there is a network latency and/or server is overloaded. Do you see any pattern in those 503 errors? Does it happen in your custom code or accessing third party services?[/quote:4fd135d3ac]
Currrenty there is no pattern though it does happen when accessing custom code or the back end webservices. Right now, we are experiencing them with 1 person calling into the server, so it wouldn't appear to be a pure load, and often it if preceeded by a large "pause" before returning, though we are having a hard time to pin it down.
With them being random and intermittent, it is hard to pinpoint, but we are going to try and run some HTTP testing tools against it so that we can record the responses from the Application server and see if we can generate one manually.
We are also moving to 3.4.3 tonight to at least get to supported version.
Any other thoughts/comments for now?
Thanks,
Kit
Subject: RE: Random 503...
Replied by: Michael Bochynski on 01-12-2005 08:53:10 PM
HI Kit,
Since it happens with custom code and backend services, I strongly suggest looking into those components. It seems that it takes "too long" for those components to finish tasks and that's why you get 503 errors.
note that this doesn't have to be under load. If, for example, you have an element which does heavy computations, or access a remote database, the processing might take a long time even with one caller.
I'd suggest looking into network latency issues and/or custom code, whether a response can be produced much sooner. While it might look like the call is stuck in Audium Call Services, the actual processing might be in either in your code or waiting for an external system to respond.
Note that most voice browsers have very short timeout time, sometimes about 10 seconds, and when the response is not delivered in that time, an error will be thrown.
Thanks,
Michael
Subject: RE: Random 503...
Replied by: null on 13-12-2005 07:33:54 PM
Since it happens with custom code and backend services, I strongly suggest looking into those components. It seems that it takes "too long" for those components to finish tasks and that's why you get 503 errors.[/quote:c4c2cdafdf]
As way of follow up, upgrading from pre-release 3.4.2 to released 3.4.3 call services appears to have eliminated all the random 503 errors we were encountering.
Subject: RE: Random 503...
Replied by: Michael Bochynski on 13-12-2005 07:36:48 PM
Hi,
Nice to hear that the issue is solved!
Regards,
Michael
