All the certified J2EE application servers provided by the usual commercial vendors (IBM; BEA; SUN;...) supports JMS as this is part of the J2EE standard. So on top of which platform are you currently runnning Jahia? If you run Jahia on top of Tomcat, why would you prefer a commercial JMS server but are using an open source servlet container? And you also have commercial companies supporting open source (JMS) implementations (e.g. Jboss)?
Else we may switch to JGroups in the near future for performance reasons (at the place of JMS) so, make sure, if you do not take a low cost open source solution, to verify that your commercial vendor also support JGoups else you may loose your investment.
Cheers,
St�phane
At 14:19 02/05/2005, you wrote:
Hi,
Thank you for your answer and your experience with OpenJMS. Your answers seem oriented on Open Source implementation. We are searching for a commercial product with support. Do you have any suggestions in this way?
Thank again for your time.
De : St�phane Croisier [ mailto:[EMAIL PROTECTED]]
Envoy� : 2 mai 2005 03:59
� : [email protected]
Objet : RE: Jahia Clustering - JMS
Yes,
We mainly tested it with OpenJMS but you may perfectly use any other open source or commercial JMS implementation (e.g. for the open source ones: http://www.manageability.org/blog/stuff/open-source-jms-java/view)
Cheers
St�phane.
At 01:40 02/05/2005, you wrote:
Hi Douglas,
We are currently in the middle of deploying a Jahia cluster using OpenJMS ( http://openjms.sourceforge.net/) as per the Jahia HOWTO on clustering.
So far, it's working very well.
One problem with OpenJMS: currently it does not support automatic failover so without some other mechanism set up to allow for this it is not possible to make a fully redundant cluster. OTOH, its purpose is to sync the cache: therefore it is a necessary component to sync changes that are made to the site. Changes to the site we are building will not happen overnight or over the weekend so in practice we will always be able to fix the JMS server before it becomes a problem with the live content.
HTH,
Chris
