java.lang.NullPointerException

null

Samebug tips1

Elasticsearch 1.x and 2.x nodes are not compatible, make sure your setup contains nodes of the same major version.

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web20387

  • null
  • via GitHub by todoubaba
    , 1 year ago
    null
  • null
  • Stack trace

    • java.lang.NullPointerException: null at org.elasticsearch.transport.netty.MessageChannelHandler.handleException(MessageChannelHandler.java:179)[elasticsearch-2.4.4.jar:2.4.4] at org.elasticsearch.transport.netty.MessageChannelHandler.handlerResponseError(MessageChannelHandler.java:174)[elasticsearch-2.4.4.jar:2.4.4] at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:122)[elasticsearch-2.4.4.jar:2.4.4] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)[netty-3.10.6.Final.jar:na] at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)[netty-3.10.6.Final.jar:na] at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)[netty-3.10.6.Final.jar:na] at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)[netty-3.10.6.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)[netty-3.10.6.Final.jar:na] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)[netty-3.10.6.Final.jar:na] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)[netty-3.10.6.Final.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_112] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_112] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_112]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago