WAITING at sun.misc.Unsafe.park(Native Method)

by

unsafe.park is pretty much the same as thread.wait, except that it’s using architecture specific code (thus the reason it’s ‘unsafe’). unsafe is not made available publicly, but is used within java internal libraries where architecture specific code would offer significant optimization benefits. It’s used a lot for thread pooling.

So, to answer your question, all the thread is doing is waiting for something, it’s not really using any CPU. Considering that your original stack trace shows that you’re using a lock I would assume a deadlock is going on in your case.

Yes I know you have almost certainly already solved this issue by now. However, you’re one of the top results if someone googles sun.misc.unsafe.park. I figure answering the question may help others trying to understand what this method that seems to be using all their CPU is.

More Related Contents:

  1. Synchronization vs Lock
  2. What is adaptive spinning w.r.t lock acquisition?
  3. Run Java Threads sequentially
  4. ExecutorCompletionService? Why do need one if we have invokeAll?
  5. How to wait for all threads to finish, using ExecutorService?
  6. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  7. Why is creating a Thread said to be expensive?
  8. When and how should I use a ThreadLocal variable?
  9. What is the difference between Thread.start() and Thread.run()?
  10. Are static variables shared between threads?
  11. How do synchronized static methods work in Java and can I use it for loading Hibernate entities?
  12. Is iterating ConcurrentHashMap values thread safe?
  13. Why use a ReentrantLock if one can use synchronized(this)?
  14. Is it safe to get values from a java.util.HashMap from multiple threads (no modification)?
  15. Is ConcurrentHashMap totally safe?
  16. How do I implement task prioritization using an ExecutorService in Java 5?
  17. Constructor synchronization in Java
  18. More efficient way for pausing loop wanted
  19. Javafx: Difference between javafx.concurent and Platform.runLater?
  20. Instruction reordering & happens-before relationship [duplicate]
  21. Why should I use concurrent characteristic in parallel stream with collect?
  22. ThreadPoolExecutor Block When its Queue Is Full?
  23. How Threadpool re-use Threads and how it works
  24. Concurrent JUnit testing
  25. Whether to use invokeAll or submit – java Executor service
  26. Handling Exceptions for ThreadPoolExecutor
  27. Is having a single threadpool better design than multiple threadpools
  28. LinkedBlockingQueue vs ConcurrentLinkedQueue
  29. Does a breakpoint halt all threads?
  30. Are 64 bit assignments in Java atomic on a 32 bit machine?

Leave a Comment