java.lang.NullPointerException at AbstractGenericHandler.java:588

Java SDK
1

Hello,
I am seeing this warning print on my application logs periodically, have tried finding the root cause for this but I am unable to do so. Can someone pls explain why such a thing would even happen?

This is the stack trace:

An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.lang.NullPointerException
at com.couchbase.client.core.endpoint.AbstractGenericHandler.populateInfo(AbstractGenericHandler.java:588)
at com.couchbase.client.core.endpoint.AbstractGenericHandler.channelActive(AbstractGenericHandler.java:567)
at com.couchbase.client.deps.io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:230)
at com.couchbase.client.deps.io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:216)
at com.couchbase.client.deps.io.netty.channel.AbstractChannelHandlerContext.fireChannelActive(AbstractChannelHandlerContext.java:209)
at com.couchbase.client.deps.io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelActive(CombinedChannelDuplexHandler.java:412)
at com.couchbase.client.deps.io.netty.channel.ChannelInboundHandlerAdapter.channelActive(ChannelInboundHandlerAdapter.java:69)
at com.couchbase.client.deps.io.netty.channel.CombinedChannelDuplexHandler.channelActive(CombinedChannelDuplexHandler.java:211)
at com.couchbase.client.deps.io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:230)
at com.couchbase.client.deps.io.netty.channel.AbstractChannelHandlerContext.invokeChannelActive(AbstractChannelHandlerContext.java:216)
at com.couchbase.client.deps.io.netty.channel.AbstractChannelHandlerContext.fireChannelActive(AbstractChannelHandlerContext.java:209)
2

Hi Carlos,

What version of the Couchbase Java SDK is generating this stack trace?

Thanks,
David

3

Hi, this is coming from an application using SDK 2.7

4

Hi, this is coming from an application using SDK 2.7

Hi Carlos,

Can you please share the full version number? There should be three components, like 2.7.3, or 2.7.19. Without knowing the third version component, it’s hard to tell what code is on line 588 of AbstractGenericHandler.java.

Thanks,
David

5

Hi David, yeah sure, the version its using is 2.7.15

6

Hi Carlos,

Here’s AbstractGenericHandler.java:588 at version 1.7.15 (core-io version is one major version less than client version).

It looks like addr (which comes from Channel.remoteAddress())is null, which is usually an indication that the channel is not connected. The stack trace indicates this is happening in the channelActive method, which gets called immediately after the connection is established.

Best guess is that the connection is actually failing for some unusual reason. The client retries failed connections; if the client eventually connects successfully, you can safely ignore this warning.

Thanks,
David

1 Like
7

I am following the execution of this "populateInfo(…)"method, I see that its used a few times in the same class.
One of them is the encode(…) method which throws an exception. I am trying to see where is this method being called and this exception handled?