Question
AES behind a Load Balancer
We have a setup where AES 7.1.7 monitoring nodes on pega 7.1.8. If we give the AES node url in the configuration settings it works fine. But if we setup AES node behind the Load Balancer and give the Load Balancer VIP name in the monitored node configuration, the monitored nodes are not able to send information to AES. AES server itself is accessible through the the browser but the monitored nodes logs say that they are not able to connect. Is AES behind a load balancer supported? What is workaround for this?
I tried that but still get these errors.
20:13:46,332 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Exception in SOAPAppenderPega.sendEvent() 20:13:46,332 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Msg: Transport error: 411 Error: Length Required 20:13:46,332 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Cause: null 20:13:46,346 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Exception in SOAPAppenderPega.sendEvent() 20:13:46,346 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Msg: Transport error: 411 Error: Length Required 20:13:46,347 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Cause: null 20:14:16,369 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Exception in SOAPAppenderPega.sendEvent() 20:14:16,369 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Msg: Timeout waiting for connection 20:14:16,369 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Cause: com.pega.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connection 20:14:46,370 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Exception in SOAPAppenderPega.sendEvent() 20:14:46,370 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Msg: Timeout waiting for connection 20:14:46,370 ERROR [stderr] (PegaRULES-Batch-1) log4j:ERROR Cause: com.pega.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connection
We have NginX web server in front of JBoss. When I change the VIP to point directly at JBoss it works.
The 411 error indicates the content-header is missing. There must be a misconfiguration somewhere, where one device is configured to use chunked encoding, but the other are not. Perhaps try to disable chunked encoding on Nginx? I'm not familiar with Nginx.
can u share your nginx access log and perhaps increasing the log level if necessary?
Accepted Solution
The way Nginx is setup it expects a Kerberos ticket and we have Sentry which does SSO. So I doubt Nginx likes requests coming from a server.
I dont see any errors in access log.
Reverse DNS lookup may be causing this. Refer to SA-6665 at https://pdn.pega.com/support-articles/multiple-nodes-shown-unavailable-aes-health-dashboard
- All systems (AES and monitored nodes) were running with the default option to do a ‘reverse DNS lookup’ on every incoming SOAP message and new browser session.
- Reverse DNS is of no value when PRPC is behind a load balancer
- A new dynamic system setting was added to turn off reverse DNS lookup.
Dynamic System Setting Pega-Engine prconfig/http/reversednslookup/default was added with a value of ‘false’