Skip directly to searchSkip directly to the site navigationSkip directly to the page's main content

IBIS-Q System Documentation - System Errors

This page describes how the system handles errors. There are three internal system errors. HTTP errors occur when a URL requests a resource that is not dynamically created by the system (via the servlet mapping contained within the web.xml), If not mapped then the app server treats the request as a normal web server would. Java exceptions thrown by all but view related objects. The Exception class is used to catch and display exceptions thrown by the application. Logging also shows all exceptions thrown. see Configuration common.xml contains bean id="Default.ExceptionHandler" class="org.ibisph.mvc.ExceptionHandler" exception handling... exception handling sets some session objects that are picked up and displayed by the MVC JSP. the exception thrown, the message.


The system handles errors in many MVC errors - all standard HTML errors 404...500 Internal errors - caught these include catchable view errors like XML file not found errors, null pointers - all throws that are controller and model related - NOT contained within the actual view rendering method. internal errors - uncaught - these include view related XSLT and XML errors. These are not caught by the system and cause the ugly browser blank message.
HTTP Errors defined in web.xml - only applies to items not dynamically mapped/handled - static files...
401Unauthorized requested resource
403Forbidden resource - refused
404Resource not found
405Unsupported method for this URL
406The requested resource exists, but not in a format/type that your browser will accept.
407The proxy server needs authorization before it can proceed.
408Request timed out. The resource is in use or is temporarily unavailable or there is a network problem.
414The requested URI (URL) is too long for the server to handle.
415The server can not process the request because the request body is in an unsupported media format.
500An unexpected error occurred inside the server that prevented it from fulfilling the request.
501Requested function is not implemented by this application on this server.
502Bad internet gateway. A server acting as a gateway or proxy did not receive a valid response from an upstream server.
503The service (server) is temporarily unavailable but should be restored in the future.
504A gateway timout error has occured. A server acting as a gateway or proxy did not receive a valid response in time.
505The server does not support the version of the HTTP protocol used in the request.
java.lang.ThrowableUncaught System Run Time Exception
The information provided was retrieved on: Sun, 17 October 2021 13:52:59.

Content updated: Wed, 4 Nov 2015 09:26:28 MST