On 27/03/17 11:39, André Warnier (tomcat) wrote:
On 27.03.2017 10:56, Mark Thomas wrote:
On 27/03/17 09:26, Olaf Kock wrote:
<snip/>
Other options that I can envision is to change Jasper's implementation
to keep serving a compiled JSP until the replacement has been properly
compiled and loaded in the background (e.g. not having compilation
block
further requests to the same page). I haven't looked at the
implementation though and don't know a) if it's feasible and b) if you
like to dive that deep into the code to change tomcat's implementation.
a) is a solution I have just been thinking about. My initial impression
is that while the simple case is probably do-able, once you start
thinking about dependencies it could get very tricky, very fast.
Probably a practical case of :
https://en.wikipedia.org/wiki/No_free_lunch_theorem
I'd suggest looking at deploying as a single WAR and using parallel
deployment.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
The main problem with the rolling deployment is that the JSP folder is a
NFS shared along all the servers on the cluster, but we can manage some how.
In the case that we decide to try to extend Jasper to do this, any clue
on which is the appropriate hook to use? That is, which class modify?
Many thanks in advance,
Joan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
