Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Coderanch by Migrated From Jforum.net, 1 year ago
This exception has no message.
via Coderanch by Manoj Maniraj, 1 year ago
This exception has no message.
via https://bugzilla.redhat.com/bugzilla/ by Filip Elias, 2 years ago
java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)[?:1.8.0_91] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)[?:1.8.0_91] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[?:1.8.0_91] at java.lang.reflect.Method.invoke(Method.java:498)[?:1.8.0_91] at com.metamx.common.lifecycle.Lifecycle$AnnotationBasedHandler.stop(Lifecycle.java:337)[java-util-0.27.4.jar:?] at com.metamx.common.lifecycle.Lifecycle.stop(Lifecycle.java:261)[java-util-0.27.4.jar:?] at io.druid.cli.CliPeon$2.run(CliPeon.java:241)[druid-services-0.8.3.jar:0.8.3] at java.lang.Thread.run(Thread.java:745)[?:1.8.0_91]Caused by: java.nio.channels.ClosedChannelException at sun.nio.ch.FileLockImpl.release(FileLockImpl.java:58)[?:1.8.0_91] at io.druid.indexing.worker.executor.ExecutorLifecycle.stop(ExecutorLifecycle.java:220)[druid-indexing-service-0.8.3.jar:0.8.3] ... 8 more