Bug 1019372

Summary: Cluster node selection process do not respect whether the nodes are able to handle the EJB request
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: wfink
Component: EJBAssignee: David M. Lloyd <david.lloyd>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.1.0, 6.1.1CC: bmaxwell, david.lloyd, smumford
Target Milestone: ---   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
When a cluster did not have the same EJBs deployed on each node, client EJB invocations were sometimes routed to cluster nodes that did not have the EJBs deployed. This occurred because `ejb-client` did not confirm that a destination node was able to handle the invocation before sending the request. `ejb-client` now performs this confirmation and invocations are routed to the correct nodes as expected.
Story Points: ---
Clone Of: Environment:
Clustered EJB's
Last Closed: 2014-07-02 08:16:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description wfink 2013-10-15 15:07:32 UTC
If a cluster contains different deployments the cluster node selection process take not into account that the selected node is not able to handle the invocation.

Comment 1 JBoss JIRA Server 2013-10-15 15:08:25 UTC
jaikiran pai <jpai> made a comment on jira EJBCLIENT-93

This should fix it https://github.com/jaikiran/jboss-ejb-client/commit/8746b80db7cc2b5d0ba7448bdff7a84ebcacba67

I'll send a PR.

Comment 2 JBoss JIRA Server 2013-10-15 15:19:54 UTC
jaikiran pai <jpai> made a comment on jira EJBCLIENT-93

Pull requests sent

Comment 5 Dimitris Andreadis 2013-10-24 18:28:21 UTC
Assigning jpai EJB issues to david.lloyd. Please re-assign to Cheng or others as needed.

Comment 6 Scott Mumford 2013-11-26 03:18:41 UTC
Added Doc Note draft. Leaving flagged as '?' for verification.

Comment 7 wfink 2013-11-26 07:21:26 UTC
From my point of view the doc text was wrong. It is not that the application is not deployed but the ejb-client select a wrong node if the application is intentional not deployed on some nodes which are member of the same cluster.

Comment 10 Jan Martiska 2014-07-02 08:16:22 UTC
This is fixed in EAP 6.2...