JBoss EAP 7.3 Discovery blacklist timeout check is incorrect

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 7.3

Issue

• In the case of a two node cluster with one node down, 50% of the requests timeout and must be retried, leading to very poor performance of our application.
• Destinations that get blacklisted to be removed from the blacklist before the timeout resulting in those requests having to be retried on another node.
• It also could result in a backlisted destination from not being added back into the available destinations if one gets blacklisted and the next time it is checked that the blacklist timeout has passed, that destination would then never be removed from the blacklist.

Resolution

Upgrade to JBoss EAP 7.3 CP 5 or latest, when available.

Root Cause

This is a known issue This content is not included.JBEAP-20340, and it will fixed in EAP 7.3 CP5.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.