• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

Deadlock Detection in Production Environment  RSS feed

 
Ranch Hand
Posts: 340
2
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If there are any deadlock cases in production environment, then, how can we identify it?
 
Saloon Keeper
Posts: 4749
117
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A quick search for "jvm deadlock detection" finds https://stackoverflow.com/questions/1102359/programmatic-deadlock-detection-in-java/, which has code for programmatic deadlock detection, as well as discussion of a library that extends that for some of Java's concurrency classes.
 
Vaibhav Gargs
Ranch Hand
Posts: 340
2
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Tim.

Is it fine to put some logic to detect the deadlocks in the code? Or should we prefer some monitoring tools? What is the best practice?
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!