Upgrade jgroups from 3.2.6 to 3.2.10

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.2.0 CE B3
• Fix Version/s: 6.0.X EE, 6.1.X EE, 6.2.0 CE B3
• Component/s: Core Infrastructure, Fault Tolerance, Fault Tolerance > Clustering Framework
• Labels:
  • liferay-fixpack-platform-12-6130
• Branch Version/s:
  6.1.x, 6.0.x
• Backported to Branch:
  Committed

Upgrade jgroups and the default config of channels, make sure we are using the best combination in the protocol stack and also we have the best configurations set.

Need QA run a full cluster related features regression tests.

[Shitian "Shelton" Zhang]

PASSED Manual Testing using the following steps:

1. Use portal-ext.properties:

   cluster.link.enabled=true
   ehcache.cluster.link.replication.enabled=true
   lucene.replicate.write=true
   
   web.server.display.node=true
   cluster.executor.debug.enabled=true
   
   web.server.http.port=8080
   portal.instance.http.port=8080
   

2. Deploy ehcache-cluster-web.war.
3. Test reindex.
4. Test reset thumbnail.
5. Test basic functions.

Fixed on:
Tomcat 6.0.33 + MySQL 5.5.34. Portal 6.0.x GIT ID: 035b5724e9a6be852726b9f6fee01115fdcae121.
Tomcat 7.0.40 + MySQL 5.5.34. Portal 6.1.x EE GIT ID: fe1a5421180b80bcf281c2f72fb8c1555c717d59.
Tomcat 7.0.42 + MySQL 5.5.34. Portal master GIT ID: 7bd7a867c4eb572ac77180a9995964e6aa74d418.

No JGroups error.