Weblogic HTTP Probe

[Andrew MacDonald]

Hey guys,

Trying to set up a weblogic http probe.

I went with this and it seemed to work in the beginning but then it started crushing our managed servers. Anyway you can help me get a good working probe setup?

This is what I had.

probe http HTTP_PROBE

  port 7001

  interval 10

  passdetect interval 60

  request method get url /login.jsp

  expect status 200 299

  open 1

Thanks!

-Andy

[Cesar Roque]

Hi Andrew,

What is the problem with this probe exactly?  Please gather the output of show probe HTTP_PROBE detail

---------------------
Cesar R
ANS Team

[Andrew MacDonald]

Here is the output.

It just seems to be taxing my managed servers in a big way.

A-ACE-4700-SLB/Prod-Support# show probe HTTP_PROBE detail

probe       : HTTP_PROBE
type        : HTTP
state       : ACTIVE
description :
----------------------------------------------
   port      : 7001    address     : 0.0.0.0         addr type  : -
   interval  : 10      pass intvl  : 60              pass count : 3
   fail count: 3       recv timeout: 10
   http method      : GET
   http url         : /login.jsp
   conn termination : GRACEFUL
   expect offset    : 0         , open timeout     : 1
   expect regex     : -
   send data        : -
                ------------------ probe results ------------------
   associations ip-address      port  porttype probes   failed   passed   health

   ------------ ---------------+-----+--------+--------+--------+--------+------

   serverfarm  : WLS11-7001
     real      : 228-WLS11host1[7001]
                192.168.211.228 7001  PROBE    125      1        124      SUCCES
S

   Socket state        : CLOSED
   No. Passed states   : 1         No. Failed states : 0
   No. Probes skipped  : 1         Last status code  : 200
   No. Out of Sockets  : 0         No. Internal error: 0
   Last disconnect err :  -
   Last probe time     : Thu Mar  7 06:48:39 2013
   Last fail time      : Never
   Last active time    : Thu Mar  7 06:27:49 2013

     real      : 229-WLS11host2[7001]
                192.168.211.229 7001  PROBE    72       11       61       SUCCES
S

   Socket state        : CLOSED
   No. Passed states   : 2         No. Failed states : 1
   No. Probes skipped  : 0         Last status code  : 200
   No. Out of Sockets  : 0         No. Internal error: 0
   Last disconnect err :  -
   Last probe time     : Thu Mar  7 06:48:44 2013
   Last fail time      : Thu Mar  7 06:30:14 2013
   Last active time    : Thu Mar  7 06:40:24 2013

Thanks for any help you can provide.

-Andy

[Cesar Roque]

Hi Andy,

with taxing do you mean overloading the server?  if that's the case you can increase the frequency, right now you have this:

   interval  : 10      pass intvl  : 60              pass count : 3

   fail count: 3       recv timeout: 10

Every 10 seconds the ACE will do an HTTP connection to the server.  You can increase this frequency to 30 secods or more

---------------------
Cesar R
ANS Team

[ajayku2]

Hi Andrew,

Apart from above you can also try the following parameter :

ace/test(config-probe-http)# connection ?

  term  Configure probe connection termination parameters

ace/test(config-probe-http)# connection term forced

This will save some resource in the server.

regards,

Ajay Kumar

[Andrew MacDonald]

What will the connection term forced do?

[Jorge Bejarano]

Andy,

Here you have a reference for that:

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/probe.html

Jorge