You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have components that clean up after themselves on stopping of the application server. Such components can produce exceptions on predestroy phase and some of this exceptions where handled without logging by DUMMY implementation of DestroyErrorHandler, so it is therefore proposed to add logging for such cases.
The text was updated successfully, but these errors were encountered:
@skabashnyuk I think we don't need to add logging to each class where on pre destroy an exception may occur. The main goal is to add logging in to DestroyErrorHandler for identify potentially unreliable places.
vinokurig
added
status/in-progress
This issue has been taken by an engineer and is under active development.
and removed
status/open-for-dev
An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
labels
Jan 20, 2017
vinokurig
added
status/code-review
This issue has a pull request posted for it and is awaiting code review completion by the community.
and removed
status/in-progress
This issue has been taken by an engineer and is under active development.
labels
Feb 1, 2017
We have components that clean up after themselves on stopping of the application server. Such components can produce exceptions on predestroy phase and some of this exceptions where handled without logging by
DUMMY
implementation ofDestroyErrorHandler
, so it is therefore proposed to add logging for such cases.The text was updated successfully, but these errors were encountered: