BugLogHQ is a tool to centralize the handling of automated bug reports from multiple applications. BugLogHQ provides a unified view of error messages sent from any number of applications, allowing the developer to search, graph, forward, and explore the bug reports submitted by the applications.
Here's a fix for another problem a colleague of mine ran into again today:
If dumping the ExtraInfo fails, this will at least provide some information on why that aspect failed and deliver the rest of the data for the original exception.
A common example for this problem is if the ExtraInfo variable contains a reference to a Hibernate object that has lazily initialized properties.
In case the Hibernate session for that object has already been closed (or just plain crashed), the dump process would throw a LazyInitializationException and drag the rest of the bug report with it.
At least in this case we'll still have the message/detail information, both traces and some other data to solve the initial problem.
Since I can't simply make assumptions on which parameters were sent to the notifyService() method I can't report this inner exception as a separate bug through the regular channels and have to provide its details inline.
michael-zock
commented
10 years ago
Here's a fix for another problem a colleague of mine ran into again today:
If dumping the ExtraInfo fails, this will at least provide some information on why that aspect failed and deliver the rest of the data for the original exception.
A common example for this problem is if the ExtraInfo variable contains a reference to a Hibernate object that has lazily initialized properties. In case the Hibernate session for that object has already been closed (or just plain crashed), the dump process would throw a LazyInitializationException and drag the rest of the bug report with it.
At least in this case we'll still have the message/detail information, both traces and some other data to solve the initial problem. Since I can't simply make assumptions on which parameters were sent to the notifyService() method I can't report this inner exception as a separate bug through the regular channels and have to provide its details inline.