# Failed to determine Thread Name **URL:** \ **Category:** Elasticsearch\ **Created:** [May 16, 2012, 4:00pm UTC](https://discuss.elastic.co/t/failed-to-determine-thread-name/7721 "2012-05-16T16:00:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ronak\_Patel](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@Ronak\_Patel](https://discuss.elastic.co/u/Ronak_Patel)\ **Post date:** [May 16, 2012, 4:00pm UTC](https://discuss.elastic.co/t/failed-to-determine-thread-name/7721/1 "2012-05-16T16:00:58Z")
Hi, 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) |#] Should I be alarmed? I'm not sure how to react... ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 16, 2012, 10:38pm UTC](https://discuss.elastic.co/t/failed-to-determine-thread-name/7721/2 "2012-05-16T22:38:09Z")
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). On Wed, May 16, 2012 at 7:00 PM, Ronak Patel [ronak2121@gmail.com](mailto:ronak2121@gmail.com) wrote: > Hi, > > 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) > |#] > > Should I be alarmed? I'm not sure how to react... ---
**Author:** ![Ronak\_Patel](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@Ronak\_Patel](https://discuss.elastic.co/u/Ronak_Patel)\ **Post date:** [May 25, 2012, 3:37pm UTC](https://discuss.elastic.co/t/failed-to-determine-thread-name/7721/3 "2012-05-25T15:37:18Z")
Shay, I"m using Elasticsearch 0.19.2. Thanks for your help. On Wed, May 16, 2012 at 6:38 PM, Shay Banon [kimchy@gmail.com](mailto: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). > > On Wed, May 16, 2012 at 7:00 PM, Ronak Patel [ronak2121@gmail.com](mailto:ronak2121@gmail.com) wrote: > > > Hi, > > > > 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) > > |#] > > > > Should I be alarmed? I'm not sure how to react... ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [May 29, 2012, 7:40pm UTC](https://discuss.elastic.co/t/failed-to-determine-thread-name/7721/4 "2012-05-29T19:40:21Z")
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 Fri, May 25, 2012 at 5:37 PM, Ronak Patel [ronak2121@gmail.com](mailto:ronak2121@gmail.com) wrote: > Shay, > > I"m using Elasticsearch 0.19.2. > > Thanks for your help. > > On Wed, May 16, 2012 at 6:38 PM, Shay Banon [kimchy@gmail.com](mailto: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). > > > > On Wed, May 16, 2012 at 7:00 PM, Ronak Patel [ronak2121@gmail.com](mailto:ronak2121@gmail.com) wrote: > > > > > Hi, > > > > > > 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) > > > |#] > > > > > > Should I be alarmed? I'm not sure how to react... ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:26am UTC](https://discuss.elastic.co/t/failed-to-determine-thread-name/7721/5 "2017-07-06T03:26:26Z")
Closed on July 6, 2017, 3:26am UTC