Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Production nodes become unresponsive and drop from Load Balancer



Unresponsive nodes dropped from F5 (Load Balancer) rotation.

Error Messages

Artefacts and logs:

000000af SystemErr R com.hazelcast.core.MemberLeftException: Member [x.x.x.x]:5701 has left cluster!

000000af SystemErr R at com.hazelcast.spi.impl.BasicInvocationFuture.resolveApplicationResponseOrThrowException(

Steps to Reproduce


Root Cause

A third-party product issue. The issue started to occur when a monitoring tool (AppDynamics) was enabled.


Make the following change to the operating environment:

Remove AppDynamics monitoring of JVMs.

Published October 5, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us