NullPointerException is coming in HornetQ server logs

Solution Unverified - Updated -

Issue

We are seeing one issue where consumers are slow and lots of data is going to DLQ, sometimes we see that JMS client fails to connect to JMS server even if we restart them, moving JMS server from one server to another solves this problem. I could see a NPE too in these logs

2017-11-28T06:01:43.831+00:00@ieatrcxb6225@JMS@ERROR [org.hornetq.core.server] (New I/O worker #46, runningThread=Thread-45 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=9aab9053-d401-11e7-a5f0-ff51c4e69c35-924440514-27532753)) HQ224044: error acknowledging message: java.lang.NullPointerException#012#011at org.hornetq.core.server.impl.ServerConsumerImpl.removeReferenceByID(ServerConsumerImpl.java:898)#012#011at org.hornetq.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:835)#012#011at org.hornetq.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:731)#012#011at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:439)#012#011at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:652)#012#011at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:616)#012#011at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:574)#012#011at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:589)#012#011at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:72)#012#011at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88)#012#011at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)#012#011at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)#012#011at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:281)#012#011at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169)#012#011at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134)#012#011at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)#012#011at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)#012#011at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)#012#011at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)#012#011at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)#012#011at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)#012#011at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)#012#011at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328)#012#011at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)#012#011at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)#012#011at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)#012#011at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)#012#011at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175)#012#011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_131]#012#011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_131]#012#011at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_131]#012
2017-11-28T06:01:43.832+00:00@ieatrcxb6225@JMS@ERROR [org.hornetq.core.server] (New I/O worker #46, runningThread=Thread-45 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=9aab9053-d401-11e7-a5f0-ff51c4e69c35-924440514-27532753)) HQ224016: Caught exception: HornetQException[errorType=ILLEGAL_STATE message=null]#012#011at org.hornetq.core.server.impl.ServerConsumerImpl.individualAcknowledge(ServerConsumerImpl.java:874)#012#011at org.hornetq.core.server.impl.ServerSessionImpl.individualAcknowledge(ServerSessionImpl.java:731)#012#011at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:439)#012#011at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:652)#012#011at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:616)#012#011at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:574)#012#011at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:589)#012#011at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:72)#012#011at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88)#012#011at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)#012#011at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)#012#011at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:281)#012#011at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169)#012#011at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134)#012#011at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)#012#011at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)#012#011at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)#012#011at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)#012#011at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)#012#011at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)#012#011at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)#012#011at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328)#012#011at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)#012#011at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)#012#011at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)#012#011at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)#012#011at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:175)#012#011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_131]#012#011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_131]#012#011at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_131]#012

Environment

Red Hat JBoss Enterprise Application Platform 6.4.17 when using the new co-located backup feature.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.