Browse Our Free Resources
550 6th Av SW
821A Bloor Street West
409 Granville St
436 York Road
System errors are unexpected and usually cause unrecoverable damage to a transaction. Examples of system error are: file system out of space, out of memory exception and database connection timeout.
Follow a simple set of guidelines to report system error.
J2EE and WebSphere
J2EE lets us specify a URI (for HTML, JSP or Servlet) for an HTTP error code in the web.xml file. This helps us report problems such as 404 file not found and 401 authorization failed. Imprtant: If you are associating a URI for the 401 error code, make sure that the URI is unprotected.
WebSphere extension allows us to specify a catch all URI that is invoked when the web container catches an exception thrown from a Servlet or JSP.
Developing System Error Pages
WebSphere Studio Application Developer (WSAD) makes it easy to develop error pages and configure the web deployment descriptor.
Open the deployment descriptor by double clicking on the web.xml file. Click on the Pages tab. In the Error Pages section click on Add. Enter an HTTP error code and URI or select them from a list.
To specify the catch all error page, click on the Extensions tab. In the Default error page field, enter the JSP or HTML file name or click on Browse to pick the file name from a list.
Save the deployment descriptor settings.
Create two sets of error conditions:
System error pages are important customer service tools. You want to make sure that they are available under all conditions and contain useful information. This article shows you how to report system errors in a reliable fashion by leveraging the J2EE standard and WebSphere extensions.
Copyright © 2012-2016 Web Age Solutions Inc.