<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
+1 Achim<br>
<br>
<br>
<div class="moz-cite-prefix">El 31/07/2013 0:02, Achim Westermann
escribió:<br>
</div>
<blockquote cite="mid:51F837DD.5060308@gmx.de" type="cite">
<pre wrap="">Hi jmcl,
no. No comments from me excluding ocee. My current company spent again
and again and again and again and again efforts to circumvent buying
ocee. We set up cronjobs to delete static export files on slave servers
(which costs additional performance), I - as a former OpenCms developer
with some insight on the internals - coded a jsp to flush the caches on
the slave instances. And on a weekly turn someone passes by to let me
request that special jsp to have the cache flushed. And then they tried
to deactivate the OpenCms cache and ran into performance issues. Putting
an external cache in front of a clustered OpenCms will even get you
deeper into the mud.
And then some editor did forget or not know (as they were new to our
company) that an OpenCms cluster slave will not know about changes
witout ocee. Did not contact me and had troubles because changes were
not propagated. And again and again and again and again and again and
again I keep on manually flushing the cache on the slave cluster servers
if some editor knew that we had this "cluster - issue".
Sum up: Those 3500 bucks spent on ocee cluster... we already lost a lot
more of money to circumvent buying that. And we will never achieve a
better solution because Alkacon did work on that for many years and
constantly is fixing bugs concerning ocee cluster. This is not a fanboi
advertisement. It's just my opinion: You will never save money by trying
to implement your own OpenCms cluster. The only thing you will achieve
is to increase your level of maintenance and time to web.
In case you don't know what problems will arise when running OpenCms in
a cluster without ocee feel free to answer.
Achim
07/30/2013 05:13 PM, jmcl wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I would like to use OpenCMS in cluster.
All I need to do is use it in a scenario where *no* content is served from
the export folder. All content is served directly from the OpenCMS web app
and is, if necessary, cached on a external cache engine like Varnish.
I understand that having two OpenCMS nodes may cause problems when it comes
to *adding* or *changing* content (at least I think there can be problems).
Now, as for *serving* content would this be a problem???? I don't seen what
problems can arise from having two OpenCMSes running at the same time, as
web apps that they are, and externally balanced.
Any comments on this, that don't directly involve the OCEE module, are
welcome.
Regards.
J.
--
View this message in context: <a class="moz-txt-link-freetext" href="http://opencms.996256.n3.nabble.com/OpenCMS-8-5-2-in-Cluster-tp23501.html">http://opencms.996256.n3.nabble.com/OpenCMS-8-5-2-in-Cluster-tp23501.html</a>
Sent from the OpenCMS mailing list archive at Nabble.com.
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<br>
<b>Ramón Gavira Sáenz</b><br>
<b>Socio-Director de Operaciones y Proyectos</b><br>
<a class="moz-txt-link-abbreviated" href="http://www.sagasoluciones.com">www.sagasoluciones.com</a> <br>
<a class="moz-txt-link-abbreviated" href="http://www.templatesaga.com">www.templatesaga.com</a> <br>
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/sagasoluciones">www.facebook.com/sagasoluciones</a> <br>
</div>
</body>
</html>