Forum Discussion

Antony2015's avatar
Antony2015
Icon for Altostratus rankAltostratus
Apr 14, 2015

HTTP Health monitor

I was using a Health Monitor as below. On HTTP response 400 Bad request, it makes the pool member up and running.

 

On HTTP 503 status " Not ready", we are getting the node member as disabled but still the pool is in up status (Green)

 

monitor sap-http-55000 { defaults from http interval 30 timeout 91 dest *:55000 recv disable "Dispatcher running but no server connected!" recv "^HTTP/1.1\s(400)" send "GET /irj/portal/ HTTP/1.1 \r\nHost:x.x.xom\r\nConnection:close\r\n\r\n"

 

The monitor acted by disabling the node (10.85.183.19) on HTTP response 503 Not Ready, not expexted as per the recv disable string "Dispatcher running but no server connected!" .

 

  • About to connect() to 10.85.183.19 port 54000
  • Trying 10.85.183.19... connected
  • Connected to 10.85.183.19 (10.85.183.19) port 54000

GET /irj/portal HTTP/1.1 User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 Host: 10.85.183.19:54000 Accept: /

 

< HTTP/1.1 503 Not Ready < Connection: close < Server: SAP J2EE Engine

 

members { 10.85.183.19:54000 {} 10.85.183.29:54000 {}

 

However no new connectivity was established to the other pool member and the connctions has brokened.

 

Thanks in advance for your your kind feedback on this !

 

No RepliesBe the first to reply