Tomcat's deploy / undeploy tasks are quite speedy, but I've found
that Tomcat starts going haywire after a few dozen hot deploys like
that -- usually it runs out of memory; sometimes the old instance
doesn't undeploy cleanly, and holds on to DB connections ...
sometimes, it gets into a confused internal state where new deploys
fail with mysterious errors, and I have to delete its temp directories.
For some reason, the hot deploy seems to work flawlessly for some and
fail for others. I'm in the latter group -- I find that I have to
restart Tomcat every hour or so. And since Jetty can start from cold
in roughly the same time that it takes Tomcat to do a hot deploy....
P
On May 23, 2006, at 9:11 AM, Claudiu Pîslaru wrote:
Hi! As for long stop/start process with Tomcat service, look at my
solution below.
For development, I'm using Tomcat 5.5.9 on a Windows machine.
Initially my dev-test-cycle was:
- create/modify a file in Eclipse
- stop Tomcat
- copy (with an ant task) files in Tomcat webapps
- start Tomcat
- see the changes
All this took me about one minute and a half. Pretty annoying...
So I begun to look for jetty, but I didn't like to have different
config files for developlment (jetty) and production (tomcat).
Soon, after I found about the Tomcat Ant tasks (deploy/undeploy/
restart/etc.) I'm very satisfied with my new configuration:
- create/modify a file in Eclipse
- press one button in Eclipse*
- see the changes
All this... in 13 seconds.
* I've created a build.xml for my application which uses Tomcat Ant
tasks (undeploy/deploy) and the "magic" button is the "Run" one
(which runs my ant default task on build.xml).
Just like that, clean and simple, I'm using Tomcat in the
development process, without the need to install some Eclipse
plugin/launcher.
Regards,
Claudiu Pislaru
Carl Pelletier wrote:
hi everyone, I'm just starting a new development projet with
Tapestry 4.0 and Hibernate 3.1. I'm looking for the best local
server to install on my computer to make my development.
here are the important point for me:
1- Must be easy to install
2- Easy to deploy with ant and Eclipse.
3- Quick to start and stop.
4- Less configuration possible.
5- Must support JNDI
6- Not to much memory ungry...
Right now, I use Tomcat 5.5.17 with the service installed and I
have some problems. Use about 90mg of memory and is really long to
start and stop.
I'm considaring switching to Jetty 6, is a good idea?
Maybe some theak in tomcat maybe anough.. Please, let me know
what you think !
Thanks
Carl Pelletier
P.S> Sorry for bad english, i'm french
_________________________________________________________________
Piano music podcast: http://inthehands.com
Other interesting stuff: http://innig.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
