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
.
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
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
-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
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
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
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
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
should not use the Jetty
included w/ Cocoon in a production setting?
Thanks a lot,
Mark Lundquist
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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
10 matches
Mail list logo
