HornetQ hangs producing messages - investigating possible causes including NullPointerException
cjaniake Mar 6, 2013 3:18 PMHi all,
We are using HornetQ version 2.2.5, with no automatic failover, and from time to time our system hangs trying to enqueue messages.
We expected that the mechanism would report the failure as we have the following configuration:
client-failure-check-period = 30000
connection-ttl = 60000
and callTimeout = 2000
However, the send command is not returning any error.
On the Hornet log, we found this exception, that we believe may be the cause of the problem:
[Old I/O server worker (parentId: 2046274478, [id: 0x79f7abae, /0.0.0.0:9475])] 19:07:50,353 SEVERE [org.hornetq.core.protocol.core.ServerSessionPacketH
andler] Caught unexpected exception
java.lang.NullPointerException
at org.hornetq.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1099)
at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:440)
at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:474)
at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:496)
at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:457)
at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:459)
at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73)
at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100)
at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362)
at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:514)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287)
at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169)
at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134)
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362)
at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:357)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:90)
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181)
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)
This other exception also happens sometimes:
[Old I/O server worker (parentId: 2046274478, [id: 0x79f7abae, /0.0.0.0:9475])] 16:56:19,051 SEVERE [org.hornetq.core.protocol.core.ServerSessionPacketH
andler] Caught unexpected exception
java.lang.NullPointerException
[Old I/O server worker (parentId: 2046274478, [id: 0x79f7abae, /0.0.0.0:9475])] 16:56:19,052 SEVERE [org.hornetq.core.protocol.core.ServerSessionPacketH
andler] Caught unexpected exception
java.lang.NullPointerException
[Old I/O server worker (parentId: 2046274478, [id: 0x79f7abae, /0.0.0.0:9475])] 16:56:19,054 SEVERE [org.hornetq.core.protocol.core.ServerSessionPacketH
andler] Caught unexpected exception
java.lang.NullPointerException
[Old I/O server worker (parentId: 2046274478, [id: 0x79f7abae, /0.0.0.0:9475])] 16:56:19,054 SEVERE [org.hornetq.core.protocol.core.ServerSessionPacketH
andler] Caught unexpected exception
java.lang.NullPointerException
If necessary, we can post the entire log file for analysis.
We appreciate any help, thank you.