JBoss EAP 7.3 Discovery blacklist timeout check is incorrect

Solution Verified - Updated -


  • 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.


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

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In