ElasticSearch has been working great when all of a sudden today; I started
seeing these exceptions in my client logs:
[#|2012-05-16T11:20:38.287-0400|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=90;_ThreadName=Thread-2;|16
May 11:20:38 WARN [util.ThreadRenamingRunnable] - Failed to determine the
thread name
java.lang.NullPointerException
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.getNewThreadName(ThreadRenamingRunnable.java:116)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:85)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
|#]
Thats strange..., its coming from netty library, for some reason the thread
renaming logic there is null... . Which version of ES are you using (so I
will know which netty lib to check).
Elasticsearch has been working great when all of a sudden today; I started
seeing these exceptions in my client logs:
[#|2012-05-16T11:20:38.287-0400|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=90;_ThreadName=Thread-2;|16
May 11:20:38 WARN [util.ThreadRenamingRunnable] - Failed to determine the
thread name
java.lang.NullPointerException
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.getNewThreadName(ThreadRenamingRunnable.java:116)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:85)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
|#]
On Wed, May 16, 2012 at 6:38 PM, Shay Banon kimchy@gmail.com wrote:
Thats strange..., its coming from netty library, for some reason the
thread renaming logic there is null... . Which version of ES are you using
(so I will know which netty lib to check).
Elasticsearch has been working great when all of a sudden today; I
started seeing these exceptions in my client logs:
[#|2012-05-16T11:20:38.287-0400|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=90;_ThreadName=Thread-2;|16
May 11:20:38 WARN [util.ThreadRenamingRunnable] - Failed to determine the
thread name
java.lang.NullPointerException
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.getNewThreadName(ThreadRenamingRunnable.java:116)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:85)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
|#]
It seems like getting the current thread in the netty code returned null..,
you can safely ignore this failure, btw, nothing bad will happen from it,
though it is strange that the current thread returned is null..., which JVM
version are you using?
On Wed, May 16, 2012 at 6:38 PM, Shay Banon kimchy@gmail.com wrote:
Thats strange..., its coming from netty library, for some reason the
thread renaming logic there is null... . Which version of ES are you using
(so I will know which netty lib to check).
Elasticsearch has been working great when all of a sudden today; I
started seeing these exceptions in my client logs:
[#|2012-05-16T11:20:38.287-0400|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=90;_ThreadName=Thread-2;|16
May 11:20:38 WARN [util.ThreadRenamingRunnable] - Failed to determine the
thread name
java.lang.NullPointerException
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.getNewThreadName(ThreadRenamingRunnable.java:116)
at
org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:85)
at
org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
|#]
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.