http-webtest-general

[Http-webtest-general] Status codes

[William M. <wi...@kn...>]

Hi Ilya,

Well, I posted a message to libwww but nobody took up the question. I 
guess it's working ok for them and I'll just have to learn to live with 
apparently bogus 500 errors when the script running on my workstation 
cannot get a connection to the remote web server. Interestingly, I 
received a different error this morning that indicated a timeout condition 
had occurred:

   STATUS CODE CHECK
    Expected '200' and got: 500 read timeout                     FAIL

I'm not sure why I'd get the above error sometimes and the "could not 
connect" error I reported earlier this week at other times. I have error 
logs which show a could not connect in the first test followed by three 
successful tests, so it's obviously not a problem with my server esp. 
since my server error logs are clean. Fortunately, I've tracked down my 
bug and can turn down the volume of testing to a reasonable level (I was 
testing every minute).

Cheers!
William

-- 
 Lead Developer
 Knowmad Services Inc. || Internet Applications & Database Integration
 http://www.knowmad.com
 

[Http-webtest-general] Re: Status codes

[Ilya M. <il...@ma...>]

>>>>> On Fri, 4 Oct 2002 11:38:42 -0400, "William McKee" <wi...@kn...> said:

WM> Hi Ilya,
WM> Well, I posted a message to libwww but nobody took up the question. I 
WM> guess it's working ok for them and I'll just have to learn to live with 
WM> apparently bogus 500 errors when the script running on my workstation 
WM> cannot get a connection to the remote web server. Interestingly, I 
WM> received a different error this morning that indicated a timeout condition 
WM> had occurred:

WM>    STATUS CODE CHECK
WM>     Expected '200' and got: 500 read timeout                     FAIL

WM> I'm not sure why I'd get the above error sometimes and the "could not 
WM> connect" error I reported earlier this week at other times. I have error 
WM> logs which show a could not connect in the first test followed by three 
WM> successful tests, so it's obviously not a problem with my server esp. 
WM> since my server error logs are clean. Fortunately, I've tracked down my 
WM> bug and can turn down the volume of testing to a reasonable level (I was 
WM> testing every minute).

As I understand LWP can encounter two types of timeouts:

1) timeout while waiting for connection
2) timeout after connecting waiting for response

I would expect #2 to be more rare than #1.

-- 
Ilya Martynov,  il...@ip...
CTO IPonWEB (UK) Ltd
Quality Perl Programming and Unix Support
UK managed @ offshore prices - http://www.iponweb.net
Personal website - http://martynov.org

[Http-webtest-general] Re: Status codes

[William M. <wi...@kn...>]

On 8 Oct 2002 at 18:39, Ilya Martynov wrote:
> WM>    STATUS CODE CHECK
> WM>     Expected '200' and got: 500 read timeout                     FAIL
> As I understand LWP can encounter two types of timeouts:
> 
> 1) timeout while waiting for connection
> 2) timeout after connecting waiting for response
> 
> I would expect #2 to be more rare than #1.


Ahh, that makes sense. So perhaps the error message above was generated by 
the #2 timeout since I've only seen it once whereas the 500 error 
connecting to remote host was more common.

Thanks,
William

-- 
 Lead Developer
 Knowmad Services Inc. || Internet Applications & Database Integration
 http://www.knowmad.com