Message:
The following issue has been reopened.
Reopener: Chris Holmes
Date: Thu, 5 Feb 2004 2:04 PM
Sorry, I wasn't too clear on this (since when I was making these early ones I just assumed I would be the one to close them). What I'm talking about here is what the client actually sees in a service exception report returned when geoserver messes up. If GeoServer messes up now, the client app that sent the request gets a service exception with the message being a whole big long stack trace. This is great for us, but from a client perspective is too much information that they don't care about. In a production environment the client should probably recieve just a message - such as "featureType 'lakes' not found". In the admin's logs there should be the full stack trace, so they can just sync up the message sent to the client with the full stack trace of their logs. That way the client doesn't see a bunch of at org.vfny... line 34 on their screen. GeoServer admins should be able to configure this, since developers would very much like to be able to have the instant feedback, but a client out in the world would not. Also, I haven't had the best of luck using the logger to log exceptions - I can't get them to do the full stack trace, it tends to eat the nested exceptions. The code in ServiceException does print everything, so I think that it should do the logging, using its method to print the xml instead of relying on the logger which I can't get to really print everything.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=GEOS-26
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GEOS-26
Summary: Add user config option to print full stack trace
Type: Improvement
Status: Reopened
Priority: Minor
Original Estimate: 40 minutes
Time Spent: Unknown
Remaining: 40 minutes
Project: GeoServer
Components:
Configuration
Fix Fors:
1.2-beta
Versions:
1.1.0
Assignee: Chris Holmes
Reporter: Chris Holmes
Created: Tue, 16 Dec 2003 7:31 PM
Updated: Thu, 5 Feb 2004 2:04 PM
Description:
Right now all service exceptions return full stack traces. This is great for debugging, but not ideal from a user perspective, a bunch of garbage about what went wrong. The geoserver admin should be able to configure whether the exceptions print full stack traces. All errors should also be logged in one place, like Abstract Service, and no other places.
Would also be nice if programming errors printed full stack traces, but I don't think that's really possible any more, as we no longer wrap known errors as quickly.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira