RE: [WEB400] missing error messages on WEB 3.5.x

["Eyers, Daniel" <daniel.eyers@xxxxxxxxxxxxx>]

What's frustrating is that we *should* be getting an error message (via
http).  It aids in debugging (JSPs are already difficult to debug).

My apps are already set to use the ErrorReporter... I wonder if
ErrorReporter is not doing it's job....

two steps forward, one step back..... :-(

dan


-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
Sent: Friday, November 16, 2001 12:02 PM
To: web400@midrange.com
Subject: RE: [WEB400] missing error messages on WEB 3.5.x


This is at least partially the province of the error reporter.  I don't use
V5R1, but if you're still using V3.5 of WebSphere, you should still be able
to change the error reporter using the adminclient.  Fire it up, and select
your web application (that's the fifth level down, domain -> node ->
application server -> servlet engine -> web application).  Go to the
"Advanced" tab, and change the setting for "Default Error Page" to
"/ErrorReporter" (no quotes).

Although all I get from this is the fact that it failed in compile.  I still
go look in the standard error log to find the actual problem.

Joe Pluta
www.plutabrothers.com


> -----Original Message-----
> From: Eyers, Daniel
>
> When a jsp failed to compile, we used to get an error message, telling us
> where the problem was...
>
> Recently, that is no longer occuring....  we just migrated to V5R1 but I'm
> not sure that's the problem...

_______________________________________________
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/web400
or email: WEB400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.