-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
Greg Barish <[EMAIL PROTECTED]> wrote:
>...
>Related to this question, I have my own question:
>
>I have 2 servlets: "PainfullyLongInit" and "ErrorProne".
>
>I have to fix and repair "ErrorProne" often - like 2 times a day.
>No problem, I just recompile and - presto - the new servlet is
>automatically picked up (via auto-reload JServ property).
>However, recompilation and then access to the new version of
>"ErrorProne" causes "PainfullyLongInit" to re-init(), thus tying
>up my whole system. I cannot even execute the new version
>of "ErrorProne" until the init() for "PainfullyLongInit" finishes.
>
>I must be doing something utterly stupid - can someone please
>enlighten me?
All servlets in a serlvet zone get unloaded if any class file in that zone
is modified and you have autoreload enabled for that zone. I think that the
only solution is to put PainfullyLongInit in a different zone from
ErrorProne, or to put PainfullyLongInit in the system classpath
(wrapper.classpath for automatic mode) so that it is not reloaded at all
except on server restart.
-- Ari Halberstadt mailto:[EMAIL PROTECTED] <http://www.magiccookie.com/>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
