Hi Christopher,
Ouch. Why do you delete the application before you stop
Tomcat? I would stop Tomcat and then delete the files.
We delete the war file before stopping tomcat to give Tomcat a chance to
auto-undeploy the application automatically.
I just read last night that
just a side note, the recommended deployment for production
environment isn't a war file. instead put the webapp folder directly
under webapps (or whenever your docroot directory is) AND put
precompiled jsps under work.
regards
Leon
On 8/6/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi
A
Hi Leon,
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: 07 August 2007 09:40
To: Tomcat Users List
Subject: Re: Best practice application deployement
just a side note, the recommended deployment for production
environment isn't a war file. instead put
:-)
regards
Leon
On 8/7/07, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Hi Leon,
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: 07 August 2007 09:40
To: Tomcat Users List
Subject: Re: Best practice application deployement
just a side note, the recommended
then copying a directory or larger collection of files.
Regards
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: 07 August 2007 10:58
To: Tomcat Users List
Subject: Re: Best practice application deployement
I concluded that from statements from Remy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerhardus,
[EMAIL PROTECTED] wrote:
Ouch. Why do you delete the application before you stop
Tomcat? I would stop Tomcat and then delete the files.
We delete the war file before stopping tomcat to give Tomcat a chance to
auto-undeploy the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerhardus,
[EMAIL PROTECTED] wrote:
If the jsp gets compiled once after the war files get deployed then I would
be willing for the server to be a bit less responsive for the 2 minutes or
so that it takes for the application to deploy.
The problem
Why bother un-deploying and then shutting-down? A shutdown
undeploys all applications, first, anyway. I think you're
just complicating the process.
We were just being paranoid. We were seeing issues before with tomcat
serving the wrong version of an application even though we believed we
deploy by copying files, copying one war file for me
is simpler then copying a directory or larger collection of files.
Regards
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: 07 August 2007 10:58
To: Tomcat Users List
Subject: Re: Best practice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerhardus,
[EMAIL PROTECTED] wrote:
I have auto-deploy on for production, but I only have 1
webapp per Tomcat instance, so I'm pretty sure it's not
working all that hard. I leave it on to simplify my
deployment (don't have to copy
I'm always a fan of not doing anything you don't have to.
There's no question that you will increase the performance of
your application by disabling the auto-deployment features of
Tomcat. The difference may be undetectable, but it's a simple
change, requires virtually no testing, and
Hi
A quick google showed that one could possibly use a maven plugin to
automatically deploy war files or ant.
If you have a fairly large infrastructure eg:
6 Apache clusters(two servers configured active/passive) each with about 10
Tomcats.
How would you do the following:
* Quickly deploy a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerhardus,
[EMAIL PROTECTED] wrote:
Currently when deploying a new set of war files we do the following in a
script that runs for all our servers.
rm -rf /home/admin/application-1.1.war
rm -rf /usr/share/tomcat5/webapps/application-1.1.war
sleep
13 matches
Mail list logo
