Upgrade recommendations from 1.1.0.Beta1 to 1.1.0.Final

[edwinb1]

Greetings.

When faced with the task of upgrading a mod_cluster environment from 1.1.0.Beta1 to 1.1.0.Final, should a lock-step upgrade between the HTTPD and Tomcat components be considered mandatory or can a more relaxed approach be taken? In other words, can I first upgrade HTTPD and incur a short cluster-wide outage, then follow up separately with each application-specific Tomcat group in a staggered fashion?

If any MCMP incompatibilty exists here then a lock-step would be required, just curious to hear any recommendations along these lines.

Regards,

Edwin

[jfclere]

MODCLUSTER-131 is changing the protocol to 0.2.0, you really need to update httpd first otherwise it won't work apart that I don't see any problem.