I was also surprised so we had a look into the LB and it actually does balance the load correctly.
The two nodes prconfig files were checked and they look exactly the same. So, or one of our applications is liinking directly to the o so busy appserver or we do have an issue which we haven't addressed yet. I'm looking further into it.
Hello, Lochan, we are experiencing the same issue. Could you, please, provide some more details about the SR-A94489 - we are having the same issue on Dev and we do not have load balancer, Websphere node agent is used. We are considering raising an SR.
Posted: 4 years ago
Posted: 27 Oct 2016 2:19 EDT
Lochana Durgada Vijayakumar (Lochan_DV)
Lead Technical Documentation Specialist
The main problem the issuer for that SR had, was that one node in their cluster showed that high number of PEGA0017 alerts, while the others do not have any significant number of those alerts. They searched for an explanation for that imbalance.
We found that they used a monitoring script that targeted directly that node, by avoiding the load balancer; due to the nature of that script, and the other load on that node, the PEGA0017 alerts were caused.
After they modified that monitoring script to use the load balancer so that the load was distributed evenly, they have not seen that imbalance any longer.
But it was not the script as such, but the load that it caused, together with the regular work load, that was the root cause for the PEGA0017 alerts.
In your case we recommend to have a closer look on the load on your system. So please issue a support request.