[INFRAUTILS-21] Automatic deadlock detection logging Created: 04/Nov/17 Updated: 28/Feb/18 Resolved: 30/Jan/18 |
|
| Status: | Resolved |
| Project: | infrautils |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Oxygen |
| Type: | New Feature | Priority: | High |
| Reporter: | Michael Vorburger | Assignee: | Michael Vorburger |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
AFAIK it is possible have (some level of) automated deadlock detection in the JVM. AFAIK, basically that section that you sometimes get at the end when you do jstack [-l ?] can also be programmatically used. This should make it possible to have automated logging in case of (suspected) deadlocks. http://metrics.dropwizard.io/3.2.3/manual/jvm.html makes me think that Dropwizard Metrics is already doing something like - I'll find out more about it, and how to automatically pre-configure to log for us, once I'm done with |
| Comments |
| Comment by Michael Vorburger [ 21/Dec/17 ] |
|
http://metrics.dropwizard.io/3.2.3/apidocs/com/codahale/metrics/jvm/ThreadDeadlockDetector.html |
| Comment by Michael Vorburger [ 21/Dec/17 ] |
| Comment by Michael Vorburger [ 28/Feb/18 ] |
|
This is already proving useful e.g. in |