Steven J. Owens wrote:
Peter,
On Tue, Nov 09, 2004 at 08:42:34AM +1100, Peter Johnson wrote:
We run 5 Tomcat servers (still on 4.1.x so not clustered) and use
CVS with two tags: 'stage' and 'prod'.
I'm a little unclear on what this means - do you mean branches?
Or do you mean
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Configuration Management, JSP Recompiles, War Files
On Sat, Nov 06, 2004 at 03:20:46AM -0500, Steven J. Owens wrote:
On Mon, Oct 25, 2004 at 09:15:41AM -0400, Shapira, Yoav wrote:
If I understand correctly, WAR file is just a glorified
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
One great way to approach production setups for Tomcat is one
webapp per Tomcat instance.
Restarts are then quick and easy, and no matter what
this one webapp does (OutOfMemoryErrors, malicious code,
etc.) it can't
affect others you have
Hi Steven,
We run 5 Tomcat servers (still on 4.1.x so not clustered) and use CVS
with two tags: 'stage' and 'prod'. When a push script is executed the
server pulls the appropriate version from cvs and then performs an ant
task to deploy the app, compiling any changed classes. We find that this
Peter, Yoav,
Thanks for the advice. Now if I could just ask for a letle
more... :-)
On Mon, Nov 08, 2004 at 01:14:22PM -, Peter Crowther wrote:
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
One great way to approach production setups for Tomcat is one
webapp per Tomcat
Peter,
On Tue, Nov 09, 2004 at 08:42:34AM +1100, Peter Johnson wrote:
We run 5 Tomcat servers (still on 4.1.x so not clustered) and use
CVS with two tags: 'stage' and 'prod'.
I'm a little unclear on what this means - do you mean branches?
Or do you mean that you effectively do
On Mon, Oct 25, 2004 at 09:15:41AM -0400, Shapira, Yoav wrote:
If I understand correctly, WAR file is just a glorified JAR file,
which in turn is just a glorified tar file. So unless you're
unjarring it, editing the config file and rejarring it, you can't
really muck with the config
On Sat, Nov 06, 2004 at 03:20:46AM -0500, Steven J. Owens wrote:
On Mon, Oct 25, 2004 at 09:15:41AM -0400, Shapira, Yoav wrote:
If I understand correctly, WAR file is just a glorified JAR file,
which in turn is just a glorified tar file. So unless you're
unjarring it, editing the
I try to precompile my jsp's, copy all the precompiled JSP's into a JAR file,
then delete all the JSP's. Less stuff to deploy. No surprises with respect to
caching, or missing compiles, or broken JSP's making it to production.
-Tim
Steven J. Owens wrote:
Hi folks,
I'm interested in hearing
On Sun, Oct 24, 2004 at 11:00:38PM -0400, Steven J. Owens wrote:
: I'm interested in hearing how people are dealing with
: configuration management issues.
:
: We've been running into some problems with JSP recompiles,
: particularly when the changed JSP is an included JSP.
: [snip]
until the new webapp is ready?
-Original Message-
From: QM [mailto:[EMAIL PROTECTED]
Sent: 25 October 2004 12:18
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Configuration Management, JSP Recompiles, War Files
On Sun, Oct 24, 2004 at 11:00:38PM -0400, Steven J. Owens
On Mon, Oct 25, 2004 at 12:28:27PM +0100, Allistair Crossley wrote:
: your suggestion is precisely what we do here, but it still leads to 5 minutes
: downtime (web server nice maintenance page, removing old war, unpacking new
: war takes time).
I guess my clients have always listed this as a
Hi,
If I understand correctly, WAR file is just a glorified JAR file,
which in turn is just a glorified tar file. So unless you're
unjarring it, editing the config file and rejarring it, you can't
really muck with the config settings inside it. How/where do people
normally keep the
13 matches
Mail list logo
