Bug 900480 (JBPAPP6-1423) - CLONE - Extremely slow response times in Remote EJB invocation on cluster membership change
Summary: CLONE - Extremely slow response times in Remote EJB invocation on cluster mem...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: JBPAPP6-1423
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering, EJB
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 6.1.0
Assignee: Jaikiran Pai
QA Contact: Jitka Kozana
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks: JBPAPP6-1422
TreeView+ depends on / blocked
 
Reported: 2012-05-21 14:27 UTC by Radoslav Husar
Modified: 2014-06-28 12:33 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-19 13:38:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-4844 0 Major Closed Extremely slow response times in Remote EJB invocation on cluster membership change 2013-10-14 03:59:42 UTC
Red Hat Issue Tracker JBPAPP6-1423 0 Major Closed CLONE - Extremely slow response times in Remote EJB invocation on cluster membership change 2013-10-14 03:59:42 UTC

Description Radoslav Husar 2012-05-21 14:27:28 UTC 
Affects: Release Notes
project_key: JBPAPP6

Up to date description track AS7-4844
Comment 1 Radoslav Husar 2012-05-21 14:27:29 UTC 
Link: Added: This issue Cloned from AS7-4844
Comment 2 Radoslav Husar 2012-05-21 14:28:24 UTC 
Workflow: Removed: GIT Pull Request workflow  Added: jira
Security: Added: Public
Docs QE Status: Added: NEW
Comment 3 Rajesh Rajasekaran 2012-05-21 15:59:43 UTC 
Labels: Removed: failover_testing Added: eap6_need_triage failover_testing
Comment 4 Anne-Louise Tangring 2012-05-23 18:50:53 UTC 
This issue has been triaged and decided to not block/prevent/hold the EAP 6 release. To comply with Release Criteria stating that no issues with Critical or Blocker priority setting can be open for the release, this is changed to priority Major.
Comment 5 Rajesh Rajasekaran 2012-06-06 20:50:29 UTC 
Link: Added: This issue is a dependency of JBPAPP-9290
Comment 6 Misty Stanley-Jones 2012-06-12 09:55:36 UTC 
Release Notes Docs Status: Added: Documented as Known Issue
Release Notes Text: Added: On server shutdown or crash, membership changes can take up to one minute to complete. This issue is currently under investigation.
Affects: Added: Release Notes
Comment 7 Rajesh Rajasekaran 2012-07-11 19:42:56 UTC 
Labels: Removed: eap6_need_triage failover_testing Added: eap601candidate failover_testing
Comment 8 Rajesh Rajasekaran 2012-09-20 19:43:05 UTC 
Labels: Removed: eap601candidate failover_testing Added: eap601-qe-triage
Comment 9 Anne-Louise Tangring 2012-10-08 15:06:37 UTC 
Not approved for EAP 6.0.1. If this should be reconsidered, please add the label: eap601-qe-triage
Comment 10 Anne-Louise Tangring 2012-10-08 15:06:37 UTC 
Labels: Removed: eap601-qe-triage
Comment 11 Dana Mison 2012-10-16 05:52:33 UTC 
Writer: Added: mistysj
Comment 12 Anne-Louise Tangring 2012-11-13 20:57:58 UTC 
Release Notes Docs Status: Removed: Documented as Known Issue 
Writer: Removed: mistysj 
Release Notes Text: Removed: On server shutdown or crash, membership changes can take up to one minute to complete. This issue is currently under investigation. 
Docs QE Status: Removed: NEW
Comment 14 Jitka Kozana 2013-02-25 11:30:31 UTC 
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
Comment 15 Radoslav Husar 2013-07-19 13:38:09 UTC 
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-shutdown-repl-async/60/artifact/report/failover.txt

Partially due to Infinispan 5.2.x upgrade in EAP 6.1 generation. Closing.
Note You need to log in before you can comment on or make changes to this bug.