Back to bug 1019372
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Lucas Costi | 2013-10-17 02:24:35 UTC | Doc Text | Cause: Consequence: Workaround (if any): Results: | |
| Doc Type | Bug Fix | Known Issue | ||
| Brad Maxwell | 2013-10-18 00:17:42 UTC | CC | bmaxwell | |
| John Skeoch | 2013-10-23 23:05:18 UTC | Assignee | jpai | dimitris |
| Dimitris Andreadis | 2013-10-24 18:28:21 UTC | Assignee | dimitris | david.lloyd |
| Scott Mumford | 2013-11-26 03:18:41 UTC | CC | smumford | |
| Doc Text | Cause: Consequence: Workaround (if any): Results: | In previous versions of JBoss EAP, it was found that in clusters containing nodes with differing application deployments, some applications did not get deployed (or were deployed only once, rather than on multiple nodes). This was caused by the ejb-client not confirming that the destination node could accept the deployment. This issue has been resolved with a patch to the ClusterContext class and applications now deploy as expected. | ||
| Dana Mison | 2013-11-28 06:16:53 UTC | Doc Text | In previous versions of JBoss EAP, it was found that in clusters containing nodes with differing application deployments, some applications did not get deployed (or were deployed only once | In previous versions of JBoss EAP, it was found that in clusters containing nodes with differing application deployments |
| Doc Text | , rather than on multiple nodes). This was caused by the ejb-client not confirming that the destination node could accept the deployment. This issue has been resolved with a patch to the ClusterContext class and applications now deploy as expected. | , the ejb-client select nodes which not having the needed application deployed. This could happen if a customer decide to not have a symetric deployment on all member nodes of a cluster. This was caused by the ejb-client not confirming that the | ||
| Doc Text | destination node could handle the invocation. This issue has been resolved with a patch to the ClusterContext class and invocations are now routed as expected. | |||
| CC | david.lloyd | |||
| Flags | needinfo?(david.lloyd) | |||
| CC | dmison | |||
| Doc Text | In previous versions of JBoss EAP, it was found that in clusters containing nodes with differing application deployments, the ejb-client select nodes which not having the needed application deployed. This could happen if a customer decide to not have a symetric deployment on all member nodes of a cluster. This was caused by the ejb-client not confirming that the destination node could handle the invocation. This issue has been resolved with a patch to the ClusterContext class and invocations are now routed as expected. | 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. | ||
| Dana Mison | 2014-05-27 01:30:18 UTC | CC | dmison | |
| Jan Martiska | 2014-07-02 08:16:22 UTC | Status | NEW | CLOSED |
| Target Release | --- | EAP 6.2.0 | ||
| Resolution | --- | CURRENTRELEASE | ||
| Flags | needinfo?(david.lloyd) | |||
| Last Closed | 2014-07-02 04:16:22 UTC |
Back to bug 1019372