[jboss-jira] [JBoss JIRA] (AS7-4844) Extremely slow response times in Remote EJB invocation on cluster membership change

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756415#comment-12756415 ] 

RH Bugzilla Integration commented on AS7-4844:
----------------------------------------------

Jitka Kudrnacova <jkudrnac at redhat.com> made a comment on [bug 900480|https://bugzilla.redhat.com/show_bug.cgi?id=900480]

Still present in 6.1.0.DR4 build:
http://hudson.qa.jboss.com/hudson/job/eap-6x-failover-ejb-ejbremote-shutdown-repl-async/38/artifact/report/failover.txt
                
> Extremely slow response times in Remote EJB invocation on cluster membership change
> -----------------------------------------------------------------------------------
>
>                 Key: AS7-4844
>                 URL: https://issues.jboss.org/browse/AS7-4844
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Radoslav Husar
>            Assignee: jaikiran pai
>              Labels: failover_testing
>             Fix For: 7.2.0.CR1
>
>
> 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-failover-ejb-ejbremote-shutdown-repl-async/22/artifact/report/failover.txt
> [3] http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x-failover-ejb-ejbremote-jvmkill-repl-sync/8/artifact/report/failover.txt

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