A couple suggestions --
1. Get a UPS for this machine so it doesn't die next time the power goes off.
You can usually have the UPS device trigger the machine to power down cleanly.
2. I suspect the JSP classes were generated from source the first time the
machine was up, and they didn't all get written to disk, or at least not
cleanly, when the power went out. The JVM and JRun should write the classes to
disk as soon as they're created, but if you have a lot of RAM they may not be
written out right away. This is just a theory. If you had some specific
exceptions (500 error tells me nothing--you need the underlying exception from
JRun's logs) from the JVM when trying to load these bad JSP classes I could
probably tell you a little more.
Scott Stirling
> -----Original Message-----
> From: Ramakrishnan Venkataraman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 10, 2000 8:35 PM
> To: JRun-Talk
> Subject: JSP problem after PC crash
>
>
>
> Hey all,
>
> I was wondering if someone could tell me what is going on in a situation I'm
> having...
>
> Basically, I have JSP pages set up to run under a Jrun server 3.1 on Win NT
> 4.0 server.
>
> On start, the JSP pages work fine. Then the PC crashed because of power
> failure.
>
> After the power was restored, the already accessed JSP pages all returned
> a 500 Internal server error. Servlets worked fine.
>
> Reboot of the server or restart of JRUN would not help at all.
>
> Then if I delete the jsp directory (where all compiled JSP class files are
> placed), things start working again. (Basically the JSP files are recompiled
> by JRun).
>
> Any idea what would be the root cause of the problem ?
>
> Is there some way we can avoid this ?
>
> Thanks in advance for any help.
>
> - Ramakrishnan Venkataraman
> Nortel Networks
> 408 965 7767
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
