Details
Improvement
Major
Description
Any possible Throwables should be caught during request processing. These Throwables should be logged, and if possible a 500 Internal Server Error should be send as a response to the Bridge.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
When an unexpected Throwable is thrown during request processing, done by the ReadHandler, ProcessHandler and WriteHandler, it is caught and dealt with:
- The Throwable is logged on the server end
- If an HTTP Response can still be send back to the Bridge, a 500 (Internal Server Error) is send
- If no HTTP Response can be send back, the connection is closed on the server end
Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - When an unexpected Throwable is thrown during request processing, done by the ReadHandler, ProcessHandler and WriteHandler, it is caught and dealt with:
The Throwable is logged on the server end
If an HTTP Response can still be send back to the Bridge, a 500 (Internal Server Error) is send
If no HTTP Response can be send back, the connection is closed on the server end
Marking this one as FIXED.
Just as added info: when the Bridge receives a 500 (Internal Server Error), a pop-up appears in the browser informing of the error and the Bridge is shutdown. The pop-up contains a reload button as well, which will reload the page and instantiate a new Bridge in order for the user to continue his/her work. Please note that this error will not invalidate the session.
Show
Jack Van Ooststroom
added a comment - Just as added info: when the Bridge receives a 500 (Internal Server Error), a pop-up appears in the browser informing of the error and the Bridge is shutdown. The pop-up contains a reload button as well, which will reload the page and instantiate a new Bridge in order for the user to continue his/her work. Please note that this error will not invalidate the session.
Changed Fix Version(s) to 1.7.2-SP1 and 1.8-DR#2