Re: Multiple or single cocoon instances
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 <[EMAIL PROTECTED]>, Kamal <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple or single cocoon instances
On 03.04.2008 18:44, Shahriar Aghajani wrote: I'd like to know about this too. How do people run a fleet of disparate Cocoon applications/websites on a single server? I have a hand full of Cocoon sites that I'm running on the same server, under Tomcat, each as a separate virtual host. We are running one application per Cocoon instance per Tomcat service. Anyway to minimize the memory usage? Can I move portions of the cocoon 2.2 libraries under Tomcat, and if so, will tomcat share the objects across the contexts? The only way to minimize memory is to have multiple applications running in one Cocoon instance. You can move libraries to Tomcat's shared classloader but this does save you hardly any memory since the objects are still per web application. And unless I'm forced to do this (for portals for example) I would not get started these things due to potential classloading issues. Joerg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple or single cocoon instances
Hi All, I'd like to know about this too. How do people run a fleet of disparate Cocoon applications/websites on a single server? I have a hand full of Cocoon sites that I'm running on the same server, under Tomcat, each as a separate virtual host. Anyway to minimize the memory usage? Can I move portions of the cocoon 2.2 libraries under Tomcat, and if so, will tomcat share the objects across the contexts? Thank you, Shahriar. Kamal 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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple or single cocoon instances
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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Multiple or single cocoon instances
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:[EMAIL PROTECTED] 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 --- José Miguel Vieira Centre for Computing in the Humanities King's College London 26 - 29 Drury Lane WC2B 5RL London Email: [EMAIL PROTECTED] Tel: +44 (0)20 7848 1242 Faxl: +44 (0)20 7848 2980 http://www.kcl.ac.uk/cch/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multiple or single cocoon instances
Hi In our (limited) experience, here are pros and cons of using a single instance: + better use of server resources (RAM, CPU) this is quite important; + single global configuration (servlet container, Java VM, Apache or other frontend...) + being forced to deploy global updates (to Cocoon configuration, custom components, etc.) on all apps (projects), this is good for security and performance updates; - slower, more expensive global updates (you have to test all apps on the same Cocoon) - sometimes you have to go through loops to introduce new features while maintaining compatibility with older apps. All in all, we are quite happy with a "hybrid" approach: we keep all apps in the same Cocoon, until we need such new features or such a different Cocoon configuration to warrant a branch to a new "major version" of our configuration. So we have something like 30 apps split among 3 Cocoons. The next update to one of the older projects will trigger a switch to the newest Cocoon configuration, and so on. HTH Tobia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- José Miguel Vieira Centre for Computing in the Humanities King's College London 26 - 29 Drury Lane WC2B 5RL London Email: [EMAIL PROTECTED] Tel: +44 (0)20 7848 1242 Faxl: +44 (0)20 7848 2980 http://www.kcl.ac.uk/cch/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
