https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #10 from Eugène Adell ---
(In reply to Igal Sapir from comment #0)
> Currently, one hack that many use is to launch Tomcat during the container
> build process, wait for an arbitrary length of time, e.g. 10s or 20s, and
> then shut
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #9 from Mark Thomas ---
Since this is synchronous, we can use the exit code to signal success or
failure.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #8 from Christopher Schultz ---
I have a slight objection to the term "warmup" being used, here.
Can we call it something else?
Nothing brilliant comes to mind.
"updown"?
"startstop"?
"launchtest"?
Perhaps such a special launch
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #7 from Mark Thomas ---
Thinking about this some more, I think the best way to handle this is with a
new "warmup" command. Implemented in a similar manner to configtest it would
call server.start() followed by server.stop().
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #6 from Igal Sapir ---
(In reply to Christopher Schultz from comment #5)
> (In reply to Igal Sapir from comment #4)
> > (In reply to Christopher Schultz from comment #3)
> > > I'm definitely missing something, here. Launching
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #5 from Christopher Schultz ---
(In reply to Igal Sapir from comment #4)
> (In reply to Christopher Schultz from comment #3)
> > I'm definitely missing something, here. Launching Tomcat and then shutting
> > it down saves zero time
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #4 from Igal Sapir ---
(In reply to Christopher Schultz from comment #3)
> I'm definitely missing something, here. Launching Tomcat and then shutting
> it down saves zero time on the next launch except maybe to create a
> directory
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #3 from Christopher Schultz ---
I'm definitely missing something, here. Launching Tomcat and then shutting it
down saves zero time on the next launch except maybe to create a directory or
two and unpack any WAR archives being
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #2 from Igal Sapir ---
(In reply to Mark Thomas from comment #1)
> Start and stop are synchronous. Calling start() then stop() should be
> sufficient. Doing that with the current startup scripts is a little trickier
> because you
https://bz.apache.org/bugzilla/show_bug.cgi?id=63389
--- Comment #1 from Mark Thomas ---
Start and stop are synchronous. Calling start() then stop() should be
sufficient. Doing that with the current startup scripts is a little trickier
because you need to wait for the shutdown port to open.
10 matches
Mail list logo
