Howdy, >couldn't you set up an error-page that only runs for this exception and >then >print out the parameters from that page? Or does the request not get that >far? If not write a valve/responseWrapper that catches response 500 errors >and act upon it.
It doesn't get that far. >Shouldn't your access log(if you have one) report a 500 response code for >that request? that could give you a time of occurrence and possibly the >user who requested it depending on your setup(since you have a closed >environment). Yeah: I'll look at the access log further. But because the problem is rare enough and users haven't complained, it's been on a back burner for me. Thanks for all your ideas ;) Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
