1 of 1 people found this helpful
I've seen a few things around this:
1 - there are some log settings you can set to ignore many of the health check messages, though it will disable some legitimate login messages as well.
2 - put a simple web server on the appserver (perl or something) that returns "OK" if a script returns successfully, where the script is running a blcli command that runs the blcli AppServerProfiler getAppServerDetails and point your load balancer at that and not the ports. or a ps check for the appserver processes (not as accurate), and turn down the polling interval becasue the script may not run in 3 sec.
otherwise you end up w/ the log spams
Thank you for your input.. it's quite helpful.
In the case of your point #1... do you happen to know what those log settings are?
I will look into the feasibility of doing option 2.
In the br/deployments/<instance>/log4j.properties file:
Changing "log4j.logger.com.bladelogic.mfw.net.BaseServerConnection" from INFO to ERROR will suppress stack traces resulting from invalid connections made to the (9841).
Adding "log4j.logger.com.bladelogic.auth.service.AuthSvcWorkerThread=ERROR" would take care of the Auth Service port (9840).
I believe these will do it, if not, you'll need to open up a ticket w/ support.. i know we can exclude many messages but not all.
Also, in blasadmin, you want to set the AppServiceURLs, ProxyServiceURLs to the VIP name. You may also need to set the 'validateclient ipaddr' and 'validaterequesturl' to false if you cannot pass the client ip through to the appserver.
Thank you for the wonderful response. We have something we can test and hopefully deploy to solve our problem.