While fighting a Production Down issue today, we had to stop several application instances that were locked up and not processing correctly.
As the applications shut down, it apparently triggered an error routine, and displayed an error message in an internal subroutine of the application. No big deal, this happens all the time.
What tickled my funny bone was the name of the method that generated the error:
And, yes, its connection was hosed, because the one of the problems was it had lost connection to the database.
I laughed out loud, literally, and almost bathed my monitor in the finest of office java.