EJB's node is dropped from the cluster if it is accessed during (re) start in JBoss EAP 6.3

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.4.0
    • 6.3.x

Issue

  • EJB's node is dropped from the cluster if it is accessed during (re) start in JBoss EAP 6.3
  • EJB invocations sometimes miss a re-started node for load-balancing if the node is restarted while the cluster is under load

Resolution

The problem will be fixed with a cumulative patch in 6.4.
Please apply JBoss EAP 6.4 cumulative patch (CP) 1 or any newer version.
Ensure that the related jboss-client.jar from the EAP/bin/client directory is used for standalone clients.

If it will not be possible to update your server please open a support ticket and reference this article.

Root Cause

The issue only appear if the client continue and invoke the EJB and hit exact the timeframe where the server already send the notification to the cluster but did not finished the start of the related application.
During that small timeframe there are situations where the client library did not handle the failure correct.
Because of this the server has been dropped from the client side cluster-view of one or more standalone clients or from the list of outbound-connections if other JBoss instances use this cluster as an EJB target.

This content is not included.EJB's node is dropped from the cluster if it is accessed during (re) start
Content from issues.jboss.org is not included.EJBCLIENT-132 - EJB's node is dropped from the cluster if it is accessed during (re) start

SBR
Product(s)
Components
Category
Tags

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.