+++ This bug was initially created as a clone of Bug #1050221 +++ Upgrade mod_cluster from 1.2.6.Final to 1.2.7.Final
Aaron Ogburn <aogburn> updated the status of jira MODCLUSTER-365 to Resolved
Aaron Ogburn <aogburn> updated the status of jira MODCLUSTER-365 to Closed
There are more bugs that need to be fixed for 6.3.0 so I think it should use a 1.2.8 in fact for 6.3.0
There are more customer bugs/requests that are supposed to be fixed in 1.2.8, adding some of them.
Fail., EAP 6.3.DR3 mod_cluster was not upgraded. It was supposed to be in version 1.2.8, but it is the old 1.2.6.
DR3 was bad, setting as MODIFIED for DR4
FAIL. Java libs were upgraded to 1.2.8, native libs remained the old 1.2.6.
The Solaris, Windows and HPUX were not updated (only RHEL is)
Vaclav, can you please upgrade the Solaris, Windows and HPUX builds? Thanks!
Regarding [comment 12]: It was not meant to be :-( EAP 6.3.0.ER1 contains the old mod_cluster 1.2.6 in all but RHEL zips.
I noticed the missing mod_cluster upgrade this morning, I accidentally missed this BZ yesterday, so I used this situation of missing installer and I am already having the upgraded mod_cluster bits ready, so only work remaining is to rebuild the native containers and do compose this afternoon. You will have these bits ready per your plan to test on Monday.
Fixed - Windows, HP-UX and Solaris contain now 1.2.8.Final bits.
mod_cluster has been upgraded to 1.2.8. Thanks.
Michal Babacek <mbabacek> updated the status of jira EAP6-172 to Resolved
John Doyle <jdoyle> updated the status of jira EAP6-172 to Closed