.jsp page check for HTTP monitor

Hi three,

 

 

There is a monitoring forum you could post questions like this in (Click here).

 

 

The monitoring daemon shouldn't differentiate between different page types. If you configure the send string with a valid request and set the receive string with a string found in a good response.

 

 

A typical send string would be:

 

 

GET /path/to/monitor_page.jsp?param=some_value HTTP/1.1\r\nHost: \r\nConnection: Close\r\n

 

 

The \r\n's are translated to carriage return/line feeds. The host header must be included (but not necessarily with a value) for HTTP 1.1 requests. The Connection: close header tells the server that the client won't try to re-use the TCP connection for subsequent requests. bigd appends a \r\n to the end of the send string so you don't need to include two.

 

 

And, assuming the pool member should respond with an HTTP 200, the receive string could be something like this:

 

 

200 OK

 

 

If you've tried this but see a pool member marked down when it's responding, you can enable debug logging on the monitoring daemon, bigd. From the command line, run 'b db bigd.debug enable'. To disable logging run 'b db bigd.debug disable'. The output is written to /var/log/bigdlog.

 

 

Aaron

Thanks. I will test and let you know.

The main issue I've run into with monitoring J2EE apps is that every web container I've ever thrown a request at expects a HOST header to be passed and I always specify using HTTP1.1. This is likely your issue. Aaron's post above should be a slam dunk for you.

 

 

-Matt