Bug 841894 - Upgrade 5.1.x to JGroups 3.0.11.FINAL
Summary: Upgrade 5.1.x to JGroups 3.0.11.FINAL
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: 6.0.1
Assignee: Tristan Tarrant
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-20 13:50 UTC by Tristan Tarrant
Modified: 2025-02-10 03:20 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:20:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2152 0 Major Resolved Upgrade 5.1.x to JGroups 3.0.11.FINAL 2012-09-13 07:20:21 UTC

Description Tristan Tarrant 2012-07-20 13:50:51 UTC
Comment 1 Michal Linhard 2012-07-27 11:52:57 UTC 
Tristan, I'm not sure what's to verify here, I've checked both distros:

jboss-datagrid-library-6.0.1.ER1.zip
jboss-datagrid-server-6.0.1.ER1.zip

and yes, they contain JGroups 3.0.11.Final

We've also ran hotrod client stress tests and everything seems to work fine.

Do you propose to check anything else ?
Comment 2 Tristan Tarrant 2012-07-27 11:58:38 UTC 
The fact that clustering stress tests work means all is good. Ideally we should also be running "mixed versions" tests: part of the cluster with JDG 6.0.0 and part with JDG 6.0.1
Comment 3 Michal Linhard 2012-07-30 12:33:44 UTC 
I checked interoperability of JDG.6.0.0.GA and JDG.6.0.1.ER1 by running a short hudson job, see logs here:
https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-experiments-mlinhard/256/artifact/report/run1/serverlogs.zip

starting 2xold and 2xnew servers, they formed a cluster and responded to client load for 2 minutes.

I'm marking this verfied.
Comment 6 Red Hat Bugzilla 2025-02-10 03:20:20 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.