Ivan wrote:
> Hello Joel,
>
> JServ is missing (at least) some good logging (all the Throwable
> should be logged) and 'friendly error messages' sent to the user - it
> is really frustrating to stay in front of your computer, waiting for
> the browser timeout, and you don't have a clue what's happening
> because nothing is logged (and usually this is some typo inside the
> configuration file).
I'm really surprised to hear this. I've always been impressed with
the level of logging in JServ. I've always found it to contain more
than enough information to debug any problems, configuration or
otherwise.
Furthermore, you don't have to just wait for your browser to time
out. When I'm debugging a problem, I've always got several windows open
tailing my logs, both the jserv_log(s) and the apache access and error
logs. Everything is there. The only thing this doesn't help with is
misconfiguration of logfile locations and that's to be expected.
As for sending friendly messages back to the user in the case of
failures, in my experience, information that's helpful in debugging is
not friendly to the user. The user is likely to report the problem by
reciting over the phone the contents of the stack trace and complaining
about how ugly the error looks. I'd rather have my users report that
they saw an Internal Server Error from apache and the time it occurred,
then let me look up in the logs what was going on at that time than to
listen to a stack trace over the phone and try to make sense of it.
P.S.
I've been seeing some trailing garbage on my messages to this list.
I've never seen them before when sending normal e-mail. Has anyone seen
this happen before and knows how to fix it? One person recommended I
look at my .signature file, but that's clean. My mail client is
Netscape 4.7 on AIX. Thanks.
--
Joel Bartley
IBM Global Services
Burlington, VT
[EMAIL PROTECTED]
The views expressed above belong to me and do not
necessarily represent those of IBM.
N.n+Zrxv,&Nr{ڽڥ!{ b"ݢ rbӭmZr?fm_Ϯzk:'
+) (
