[
https://issues.jboss.org/browse/WFLY-7?page=com.atlassian.jira.plugin.sys...
]
RH Bugzilla Integration commented on WFLY-7:
--------------------------------------------
Radoslav Husar <rhusar(a)redhat.com> made a comment on [bug
900480|https://bugzilla.redhat.com/show_bug.cgi?id=900480]
Latest EAP 6.1.0 runs show that this is no longer an issue. The response time increase
upon failover is minimal (especially compared to original concern when response times
could reach up to a minute).
http://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-shutd...
Partially due to Infinispan 5.2.x upgrade in EAP 6.1 generation. Closing.
Extremely slow response times in Remote EJB invocation on cluster
membership change
-----------------------------------------------------------------------------------
Key: WFLY-7
URL:
https://issues.jboss.org/browse/WFLY-7
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Reporter: Radoslav Husar
Assignee: jaikiran pai
Labels: failover_testing
Fix For: 8.0.0.Beta1
In failover scenarios [1], the response times of remote EJB client are sometimes
extremely large.
On *graceful* shutdown, response times reach up to one minute [2]. Graceful failover is a
positive test, no such exceptions are anticipated.
On server crash in a cluster, RTs reach up to 1 minute as well [3].
[1]
https://docspace.corp.redhat.com/docs/DOC-92019#Failover_Tests
[2]
http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x...
[3]
http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira