You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mark Lundquist <ml...@wrinkledog.com> on 2003/12/23 00:41:02 UTC
Jetty included w/ Cocoon
Right now, for development, I'm running Cocoon 2.1.2 inside the Jetty
that comes included w/ the Cocoon distro. Somewhere, I read something
that gave me the impression that this Jetty is somehow stripped down,
or otherwise not production-ready.
Someone must know — is there any reason why I should not use the Jetty
included w/ Cocoon in a production setting?
Thanks a lot,
Mark Lundquist
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by beyaRecords - The home Urban music <uz...@beya-records.com>.
yep, I am using ajp13. i presume cocoon folder and cocoon.war would sit
in the root of jetty as per tomcat?
Uzo
On 23 Dec 2003, at 21:14, Upayavira wrote:
> Don't understand what technique you're using to connect Apache/Tomcat.
> Are you using AJP13? If so, you can just shut down Tomcat and start up
> Jetty (making sure it's listening for AJP).
>
> Regards, Upayavira
>
> beyaRecords - The home Urban music wrote:
>
>> cheers,
>> i will now investigate jetty and see what it is like.
>>
>> i have tomcat setup with apache so that tomcat can be accessed minus
>> :8080
>>
>> so 12.0.0.1/examples leads me to the tomcat stuff
>>
>> my apache workes2.properties file reads as:
>>
>> [uri:127.0.0.1:8003]
>> info=Example virtual host. Make sure myVirtualHost is in /etc/hosts
>> to test it
>> alias=myVirtualHost:8003
>>
>> [uri:127.0.0.1:8003/ex]
>> info=Example webapp in the virtual host. It'll go to lb_1 ( i.e.
>> localhost:8019 )
>> context=/ex
>> group=lb_1
>>
>> [uri:/examples]
>> info=Example webapp in the default context.
>> context=/examples
>> debug=0
>>
>> [uri:/examples1/*]
>> info=A second webapp, this time going to the second tomcat only.
>> group=lb_1
>> debug=0
>>
>> [uri:/examples/servlet/*]
>> info=Prefix mapping
>>
>> [uri:/examples/*.jsp]
>> info=Extension mapping
>>
>> [uri:/examples/*]
>> info=Map the whole webapp
>>
>> [uri:/examples/servlet/HelloW]
>> info=Example with debug enabled.
>> debug=10
>>
>> [uri:/cocoon]
>> info=Example webapp in the default context.
>> context=/cocoon
>> debug=0
>>
>> [uri:/cocoon/*]
>> info=Map the whole webapp
>>
>> My question is, can i leave the code as is and access jetty using the
>> same settings?
>>
>>
>> Uzo
>> On 23 Dec 2003, at 20:59, Litrik De Roy wrote:
>>
>>> Upayavira wrote:
>>>
>>>> beyaRecords - The home Urban music wrote:
>>>>
>>>>> So chaps,
>>>>> is jetty a better proposition than tomcat?
>>>>
>>>>
>>>> In my installation, Tomcat failed regularly (every day or two).
>>>> Jetty fails only when the processor can't cope (bad design of my
>>>> Cocoon app).
>>>
>>>
>>> We have seen similar behavior when using Tomcat. We had to restart
>>> it multiple times per week, it was using a lot of resources (memory
>>> and CPU) and each and every upgrade we had problems with endorsed
>>> jars. Aaargh.
>>>
>>> Jetty is so much smaller, leaner and stabler.
>>>
>>>> Regards, Upayavira
>>>>
>>>>> Uzo
>>>>> On 23 Dec 2003, at 19:20, Tony Collen wrote:
>>>>
>>>>
>>> --
>>>
>>> Litrik De Roy
>>> www.litrik.com
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>>> For additional commands, e-mail: users-help@cocoon.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by Upayavira <uv...@upaya.co.uk>.
Don't understand what technique you're using to connect Apache/Tomcat.
Are you using AJP13? If so, you can just shut down Tomcat and start up
Jetty (making sure it's listening for AJP).
Regards, Upayavira
beyaRecords - The home Urban music wrote:
> cheers,
> i will now investigate jetty and see what it is like.
>
> i have tomcat setup with apache so that tomcat can be accessed minus
> :8080
>
> so 12.0.0.1/examples leads me to the tomcat stuff
>
> my apache workes2.properties file reads as:
>
> [uri:127.0.0.1:8003]
> info=Example virtual host. Make sure myVirtualHost is in /etc/hosts to
> test it
> alias=myVirtualHost:8003
>
> [uri:127.0.0.1:8003/ex]
> info=Example webapp in the virtual host. It'll go to lb_1 ( i.e.
> localhost:8019 )
> context=/ex
> group=lb_1
>
> [uri:/examples]
> info=Example webapp in the default context.
> context=/examples
> debug=0
>
> [uri:/examples1/*]
> info=A second webapp, this time going to the second tomcat only.
> group=lb_1
> debug=0
>
> [uri:/examples/servlet/*]
> info=Prefix mapping
>
> [uri:/examples/*.jsp]
> info=Extension mapping
>
> [uri:/examples/*]
> info=Map the whole webapp
>
> [uri:/examples/servlet/HelloW]
> info=Example with debug enabled.
> debug=10
>
> [uri:/cocoon]
> info=Example webapp in the default context.
> context=/cocoon
> debug=0
>
> [uri:/cocoon/*]
> info=Map the whole webapp
>
> My question is, can i leave the code as is and access jetty using the
> same settings?
>
>
> Uzo
> On 23 Dec 2003, at 20:59, Litrik De Roy wrote:
>
>> Upayavira wrote:
>>
>>> beyaRecords - The home Urban music wrote:
>>>
>>>> So chaps,
>>>> is jetty a better proposition than tomcat?
>>>
>>>
>>> In my installation, Tomcat failed regularly (every day or two).
>>> Jetty fails only when the processor can't cope (bad design of my
>>> Cocoon app).
>>
>>
>> We have seen similar behavior when using Tomcat. We had to restart it
>> multiple times per week, it was using a lot of resources (memory and
>> CPU) and each and every upgrade we had problems with endorsed jars.
>> Aaargh.
>>
>> Jetty is so much smaller, leaner and stabler.
>>
>>> Regards, Upayavira
>>>
>>>> Uzo
>>>> On 23 Dec 2003, at 19:20, Tony Collen wrote:
>>>
>>>
>> --
>>
>> Litrik De Roy
>> www.litrik.com
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by beyaRecords - The home Urban music <uz...@beya-records.com>.
cheers,
i will now investigate jetty and see what it is like.
i have tomcat setup with apache so that tomcat can be accessed minus
:8080
so 12.0.0.1/examples leads me to the tomcat stuff
my apache workes2.properties file reads as:
[uri:127.0.0.1:8003]
info=Example virtual host. Make sure myVirtualHost is in /etc/hosts to
test it
alias=myVirtualHost:8003
[uri:127.0.0.1:8003/ex]
info=Example webapp in the virtual host. It'll go to lb_1 ( i.e.
localhost:8019 )
context=/ex
group=lb_1
[uri:/examples]
info=Example webapp in the default context.
context=/examples
debug=0
[uri:/examples1/*]
info=A second webapp, this time going to the second tomcat only.
group=lb_1
debug=0
[uri:/examples/servlet/*]
info=Prefix mapping
[uri:/examples/*.jsp]
info=Extension mapping
[uri:/examples/*]
info=Map the whole webapp
[uri:/examples/servlet/HelloW]
info=Example with debug enabled.
debug=10
[uri:/cocoon]
info=Example webapp in the default context.
context=/cocoon
debug=0
[uri:/cocoon/*]
info=Map the whole webapp
My question is, can i leave the code as is and access jetty using the
same settings?
Uzo
On 23 Dec 2003, at 20:59, Litrik De Roy wrote:
> Upayavira wrote:
>
>> beyaRecords - The home Urban music wrote:
>>
>>> So chaps,
>>> is jetty a better proposition than tomcat?
>>
>> In my installation, Tomcat failed regularly (every day or two). Jetty
>> fails only when the processor can't cope (bad design of my Cocoon
>> app).
>
> We have seen similar behavior when using Tomcat. We had to restart it
> multiple times per week, it was using a lot of resources (memory and
> CPU) and each and every upgrade we had problems with endorsed jars.
> Aaargh.
>
> Jetty is so much smaller, leaner and stabler.
>
>> Regards, Upayavira
>>
>>> Uzo
>>> On 23 Dec 2003, at 19:20, Tony Collen wrote:
>>
> --
>
> Litrik De Roy
> www.litrik.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by Litrik De Roy <co...@litrik.com>.
Upayavira wrote:
> beyaRecords - The home Urban music wrote:
>
>> So chaps,
>> is jetty a better proposition than tomcat?
>
> In my installation, Tomcat failed regularly (every day or two). Jetty
> fails only when the processor can't cope (bad design of my Cocoon app).
We have seen similar behavior when using Tomcat. We had to restart it
multiple times per week, it was using a lot of resources (memory and
CPU) and each and every upgrade we had problems with endorsed jars. Aaargh.
Jetty is so much smaller, leaner and stabler.
> Regards, Upayavira
>
>> Uzo
>> On 23 Dec 2003, at 19:20, Tony Collen wrote:
>
--
Litrik De Roy
www.litrik.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by Upayavira <uv...@upaya.co.uk>.
beyaRecords - The home Urban music wrote:
> So chaps,
> is jetty a better proposition than tomcat?
In my installation, Tomcat failed regularly (every day or two). Jetty
fails only when the processor can't cope (bad design of my Cocoon app).
Regards, Upayavira
>
>
> Uzo
> On 23 Dec 2003, at 19:20, Tony Collen wrote:
>
>> Litrik De Roy wrote:
>>
>>> Mark Lundquist wrote:
>>>
>>>> Right now, for development, I'm running Cocoon 2.1.2 inside the
>>>> Jetty that comes included w/ the Cocoon distro. Somewhere, I read
>>>> something that gave me the impression that this Jetty is somehow
>>>> stripped down, or otherwise not production-ready.
>>>>
>>>> Someone must know — is there any reason why I should not use the
>>>> Jetty included w/ Cocoon in a production setting?
>>>>
>>> At the office, we have been using the Jetty included in Cocoon for
>>> quite some time now as our production server. It is not exactly a
>>> high-volume site, but Jetty handles the load perfectly. It is very
>>> stable and reliable. And it was VERY easy to set up.
>>> I'm so glad we got rid of Tomcat....
>>
>>
>> Yep... Jetty has treated me well... it is very stable. Have you
>> played with "Jetty Plus" yet? The JNDI Datasource pooling looks
>> interesting and useful.
>>
>>
>>
>> Tony
>>
>>>> Thanks a lot,
>>>> Mark Lundquist
>>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by beyaRecords - The home Urban music <uz...@beya-records.com>.
So chaps,
is jetty a better proposition than tomcat?
Uzo
On 23 Dec 2003, at 19:20, Tony Collen wrote:
> Litrik De Roy wrote:
>> Mark Lundquist wrote:
>>> Right now, for development, I'm running Cocoon 2.1.2 inside the
>>> Jetty that comes included w/ the Cocoon distro. Somewhere, I read
>>> something that gave me the impression that this Jetty is somehow
>>> stripped down, or otherwise not production-ready.
>>>
>>> Someone must know — is there any reason why I should not use the
>>> Jetty included w/ Cocoon in a production setting?
>>>
>> At the office, we have been using the Jetty included in Cocoon for
>> quite some time now as our production server. It is not exactly a
>> high-volume site, but Jetty handles the load perfectly. It is very
>> stable and reliable. And it was VERY easy to set up.
>> I'm so glad we got rid of Tomcat....
>
> Yep... Jetty has treated me well... it is very stable. Have you
> played with "Jetty Plus" yet? The JNDI Datasource pooling looks
> interesting and useful.
>
>
>
> Tony
>
>>> Thanks a lot,
>>> Mark Lundquist
>>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by Tony Collen <co...@umn.edu>.
Litrik De Roy wrote:
> Mark Lundquist wrote:
>
>> Right now, for development, I'm running Cocoon 2.1.2 inside the Jetty
>> that comes included w/ the Cocoon distro. Somewhere, I read something
>> that gave me the impression that this Jetty is somehow stripped down,
>> or otherwise not production-ready.
>>
>> Someone must know — is there any reason why I should not use the Jetty
>> included w/ Cocoon in a production setting?
>>
> At the office, we have been using the Jetty included in Cocoon for quite
> some time now as our production server. It is not exactly a high-volume
> site, but Jetty handles the load perfectly. It is very stable and
> reliable. And it was VERY easy to set up.
>
> I'm so glad we got rid of Tomcat....
Yep... Jetty has treated me well... it is very stable. Have you played with "Jetty Plus" yet? The
JNDI Datasource pooling looks interesting and useful.
Tony
>
>> Thanks a lot,
>> Mark Lundquist
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by Litrik De Roy <co...@litrik.com>.
Mark Lundquist wrote:
> Right now, for development, I'm running Cocoon 2.1.2 inside the Jetty
> that comes included w/ the Cocoon distro. Somewhere, I read something
> that gave me the impression that this Jetty is somehow stripped down,
> or otherwise not production-ready.
>
> Someone must know — is there any reason why I should not use the Jetty
> included w/ Cocoon in a production setting?
>
At the office, we have been using the Jetty included in Cocoon for quite
some time now as our production server. It is not exactly a high-volume
site, but Jetty handles the load perfectly. It is very stable and
reliable. And it was VERY easy to set up.
I'm so glad we got rid of Tomcat....
> Thanks a lot,
> Mark Lundquist
>
--
Litrik De Roy
www.litrik.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Jetty included w/ Cocoon
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le Mardi, 23 déc 2003, à 00:41 Europe/Zurich, Mark Lundquist a écrit :
> Right now, for development, I'm running Cocoon 2.1.2 inside the Jetty
> that comes included w/ the Cocoon distro. Somewhere, I read something
> that gave me the impression that this Jetty is somehow stripped down,
> or otherwise not production-ready...
Cocoon's version of Jetty is the same that you can find at
http://jetty.mortbay.org, but it does not include the full package. So
for production use it's better to have a look at Jetty's official
documentation and examples, rather than just copying our basic setup.
See also
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104928940509720&w=2
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org