Hello all,
Joel,
lets make an experiment
try default installation (Apache + JServ1.1) on Windows machine and
add just one more file to your zone.properties repository.
repositories=<default>;d:/temp/exisiting_file.zip
(note 1. Windows machine and 2. use '/' separator instead of '\')
then try to access \servlet\IsItWorking URL.
I doubt that you'll be able to quickly diagnose the problem, even if
you know the JServ sources very well.
well - give it a try - it's just a game :)
and if you take a look at the recent 'NullPointerException' thread in
this list, you will agree that friendly message
'JServ couldn't create Classloader - please check your zone.properties'
inside your browser will be much better than user waiting for his
browser to timeout, calling you, and all you can find is some
NullPointerException inside Apache error.log (and btw. it seems that
Exceptions 1. don't have timesstamp and 2. are NOT APPENEDed to
the error.log, so you may lose a lot of time till you find even that
NullPointerException :)
my experience with Java server application has learned me to:
1. catch & log ALL Throwable objects .
2. send at least 'Internal Error' message to the user.
my 2 cents :)
Thursday, January 20, 2000, 1:55:35 PM, you wrote:
JB> 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).
JB> I'm really surprised to hear this. I've always been impressed with
JB> the level of logging in JServ. I've always found it to contain more
JB> than enough information to debug any problems, configuration or
JB> otherwise.
JB> Furthermore, you don't have to just wait for your browser to time
JB> out. When I'm debugging a problem, I've always got several windows open
JB> tailing my logs, both the jserv_log(s) and the apache access and error
JB> logs. Everything is there. The only thing this doesn't help with is
JB> misconfiguration of logfile locations and that's to be expected.
JB> As for sending friendly messages back to the user in the case of
JB> failures, in my experience, information that's helpful in debugging is
JB> not friendly to the user. The user is likely to report the problem by
JB> reciting over the phone the contents of the stack trace and complaining
JB> about how ugly the error looks. I'd rather have my users report that
JB> they saw an Internal Server Error from apache and the time it occurred,
JB> then let me look up in the logs what was going on at that time than to
JB> listen to a stack trace over the phone and try to make sense of it.
JB> P.S.
JB> I've been seeing some trailing garbage on my messages to this list.
JB> I've never seen them before when sending normal e-mail. Has anyone seen
JB> this happen before and knows how to fix it? One person recommended I
JB> look at my .signature file, but that's clean. My mail client is
JB> Netscape 4.7 on AIX. Thanks.
JB> --
JB> Joel Bartley
JB> IBM Global Services
JB> Burlington, VT
JB> [EMAIL PROTECTED]
JB> The views expressed above belong to me and do not
JB> necessarily represent those of IBM.
JB>
N.n+Zrxv,&Nr{ڽڥ!{ b"ݢ rbӭmZr?fm_Ϯzk:'
JB> +) (
--
Best regards,
Ivan mailto:[EMAIL PROTECTED]
--
----------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
