cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Hohls" <DHo...@csir.co.za>
Subject Re: Multiple or single cocoon instances
Date Fri, 04 Apr 2008 07:47:51 GMT
Kamal

Good to hear this recommendation.  We certainly can't afford lots of 
hardware, we don't have lots of special Java classes ... so I think
we should keep going with our "multiple apps per one Cocoon per
one server" scenario.  We are using POT (Plain Old Tomcat) to
host Cocoon.

>>> On 2008/04/01 at 11:57, in message <47F2070A.3010607@tt.com.au>,
Kamal <kbhatt@tt.com.au> wrote:
We have multiple "applications" in one cocoon. I guess it depends on 
what you are doing, how much you can afford to spend on hardware and
how 
important is zero down time.

If you have loads of money to spend on hardware (including
maintenance), 
and you are bundling Java classes with Cocoon, then go with multiple 
instances of Cocoon. If you have one application server, what I don't 
recommend, is a scenario with multiple instances of Cocoon, all sitting

in an a single application server. This is a disaster IMHO. Cocoon is a

beast it is difficult to manage this well. Another thing I don't 
recommend is using mount tables. They seem like a good idea, but they 
are not as they are managed within Cocoon it is harder to change. In 
fact, if you are using an application server, you should try to get as

much of the application off the application server.

I am actually curious as to how people run Cocoon. That is, do you use

an application server (JBoss, SJSAS) or do people get by with Jetty.


Jeroen Reijn wrote:
>
> Hi Jose,
>
> well I guess that depends a bit on what your environment is.
> We at Hippo have used mulitple project -> 1 cocoon in the past, but 
> switched to using 1 cocoon instance per project.
>
> The problem with multiple project in 1 cocoon is that if one project

> causes your server to fail it will drag down all the others.
> Also with updates it can be more easy to update only one application

> instead of shutting down all project because 1 project needs a new 
> dependency.
>
> I guess it's more a personal taste, but a good topic IMO to see how 
> people handle their cocoon environments.
>
> Regards,
>
> Jeroen
>
> -----Original Message-----
> From: José Miguel Vieira [mailto:jose.m.vieira@kcl.ac.uk] 
> Sent: Mon 3/31/2008 11:37 AM
> To: users@cocoon.apache.org 
> Subject: Multiple or single cocoon instances
>
> Hello,
>
> At the moment we have several cocoon projects, about 20 or so,
running 
> inside the same cocoon, version 2.1.10.
>
> Is this the best way to do it, or would it be better to have one 
> cocoon instance per project?
>
> Thanks,
> Miguel
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org 
For additional commands, e-mail: users-help@cocoon.apache.org 


-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice,
and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message