Try following :
1. In WebSphere setup , set the Java Maximum Heap size and Stack size to
reasonably high value.
2. make sure that the jsp path is in classpath.
Thanks
RajaKumar
> -----Original Message-----
> From: Mike Herron [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, January 03, 2000 4:03 PM
> To: [EMAIL PROTECTED]
> Subject: Why do we have to restart after every change to a JSP?
>
> Every time we change a JSP we need to restart WebSphere (2.03). Why? Is
> there a way to fix this?
>
> We're going nuts restarting the damn WebSphere service every time we make
> a
> tiny change in a JSP.
>
> After making a change to a JSP, we get one of the following two behaviors:
>
>
> 1. "500 Internal Server Error" and "The servlet named pageCompile at
> the requested URL reported this exception
> pagecompile._product__group__assignment_xjsp: null."
>
> 2. a badly-parsed version of the JSP page -- to me, it looks like
> WebSphere is not
> parsing the JSP properly -- we see some Java code, mixed in with HTML
> code,
> in Netscape when we try to view that JSP.
>
> Anybody?? PLEASE HELP!!!
>
> Mike
> [EMAIL PROTECTED]
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
