Hi.
I am far from being the specialist here, but my inner application
designer core revolts at the idea of having a thread in Tomcat busy at
nothing else but checking 86,400 times a day, just in case you redeploy
an application from time to time.
There must exist a more efficient mechanism for doing that.
One should probably check how the Tomcat Manager deploys an application
on-demand, and use the same mechanism e.g.
I'm curious to see Chuck's reaction to this thread.
Khlystov Alexandr wrote:
I have 10 seconds now instead of 15 with 2 of 3 options:
backgroundProcessorDelay="1"
<Context docBase="hello-webapp" path="/hello-webapp" reloadable="true"
antiJARLocking="true" backgroundProcessorDelay="1"/>
and
lazy-init for all beans.
Cool! thanks again.
Now I'm going to sleep, and will implement javac direct compilation
tomorrow.
Kees Jan Koster пишет:
Dear Khlystov,
1. 5 second (using maven) compile source ( usually it is 1 or 2 files )
2. 0 second copy *.class file into Tomcat/webapps
Stop using Maven for simple compiles and write a small shell script
that just calls javac with the webapp's WEB-INF/classes as output dir.
3. 5-7 seconds waiting while Tomcat finds that my webapp deployed
files are changed
There is a timer somewhere that you can lower for this. I forget
precisely which one. It will slow down Tomcat a bit, but you will
redeploy faster.
4. 1 seconds takes to undeploy my webapp
5. 3-5 seconds takes to deploy ( really initialize Wicket & Spring
Beans frameworks with my data)
Well, you chose these frameworks, so you'll have to live with their
startup times. Lazy initialisation *may* help, if you initialise more
than you need for a specific test.
--
Kees Jan
http://java-monitor.com/forum/
[email protected]
06-51838192
Rule 1 for being in a hole: stop digging.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
