java.lang.IndexOutOfBoundsException: writerIndex(117) + minWritableBytes(8) exceeds maxCapacity(118): SlicedByteBuf(ridx: 0, widx: 117, cap: 118/118, unwrapped: UnpooledHeapByteBuf(ridx: 118, widx: 118, cap: 496))

JBoss Issue Tracker | Andeka Putra | 1 year ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    I have an application that embeds hornetq-2.4 with netty acceptor and uses netty-4.0 for other use as well. When I upgraded netty to version >= 4.0.28, hornetq server throws a java.lang.IndexOutOfBoundsException when a client tries to read a message. Full exception snapshot: 21:52:58.118 [Thread-5 (HornetQ-server-HornetQServerImpl::serverUUID=42c1c7d8-5174-11e5-828a-1b48920727f8-345902941)] WARN org.hornetq.core.server - HQ222151: removing consumer which did not handle a message, consumer=ServerConsumerImpl [id=0, filter=null, binding=LocalQueueBinding [address=queue.transactionQueue, queue=QueueImpl[name=queue.transactionQueue, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=42c1c7d8-5174-11e5-828a-1b48920727f8]]@411f53a0, filter=null, name=queue.transactionQueue, clusterName=queue.transactionQueue42c1c7d8-5174-11e5-828a-1b48920727f8]], message=Reference[41]:RELIABLE:ServerMessage[messageID=41,durable=true,userID=null,priority=4, bodySize=118,expiration=0, durable=true, address=queue.transactionQueue,properties=TypedProperties[null]]@309000709 java.lang.IndexOutOfBoundsException: writerIndex(117) + minWritableBytes(8) exceeds maxCapacity(118): SlicedByteBuf(ridx: 0, widx: 117, cap: 118/118, unwrapped: UnpooledHeapByteBuf(ridx: 118, widx: 118, cap: 496)) at io.netty.buffer.AbstractByteBuf.ensureWritable(AbstractByteBuf.java:242) ~[netty-all-4.0.28.Final.jar:4.0.28.Final] at io.netty.buffer.AbstractByteBuf.writeLong(AbstractByteBuf.java:790) ~[netty-all-4.0.28.Final.jar:4.0.28.Final] at io.netty.buffer.WrappedByteBuf.writeLong(WrappedByteBuf.java:576) ~[netty-all-4.0.28.Final.jar:4.0.28.Final] at org.hornetq.core.buffers.impl.ChannelBufferWrapper.writeLong(ChannelBufferWrapper.java:605) ~[hornetq-commons-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.wireformat.SessionReceiveMessage.encode(SessionReceiveMessage.java:71) ~[hornetq-core-client-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.ChannelImpl.send(ChannelImpl.java:230) ~[hornetq-core-client-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBatched(ChannelImpl.java:205) ~[hornetq-core-client-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.CoreSessionCallback.sendMessage(CoreSessionCallback.java:76) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:942) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:398) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:2544) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:2137) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl.access$1300(QueueImpl.java:81) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:2917) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) [hornetq-core-client-2.4.3.Final.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60] I know this is a rather unlikely ehancement request considering that hornetq-2.4.7 actually uses netty-4.0.13. But if someone can fix this issue or at least guide me on how to fix it, I would very much appreciate it.

    JBoss Issue Tracker | 1 year ago | Andeka Putra
    java.lang.IndexOutOfBoundsException: writerIndex(117) + minWritableBytes(8) exceeds maxCapacity(118): SlicedByteBuf(ridx: 0, widx: 117, cap: 118/118, unwrapped: UnpooledHeapByteBuf(ridx: 118, widx: 118, cap: 496))
  2. 0

    I have an application that embeds hornetq-2.4 with netty acceptor and uses netty-4.0 for other use as well. When I upgraded netty to version >= 4.0.28, hornetq server throws a java.lang.IndexOutOfBoundsException when a client tries to read a message. Full exception snapshot: 21:52:58.118 [Thread-5 (HornetQ-server-HornetQServerImpl::serverUUID=42c1c7d8-5174-11e5-828a-1b48920727f8-345902941)] WARN org.hornetq.core.server - HQ222151: removing consumer which did not handle a message, consumer=ServerConsumerImpl [id=0, filter=null, binding=LocalQueueBinding [address=queue.transactionQueue, queue=QueueImpl[name=queue.transactionQueue, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=42c1c7d8-5174-11e5-828a-1b48920727f8]]@411f53a0, filter=null, name=queue.transactionQueue, clusterName=queue.transactionQueue42c1c7d8-5174-11e5-828a-1b48920727f8]], message=Reference[41]:RELIABLE:ServerMessage[messageID=41,durable=true,userID=null,priority=4, bodySize=118,expiration=0, durable=true, address=queue.transactionQueue,properties=TypedProperties[null]]@309000709 java.lang.IndexOutOfBoundsException: writerIndex(117) + minWritableBytes(8) exceeds maxCapacity(118): SlicedByteBuf(ridx: 0, widx: 117, cap: 118/118, unwrapped: UnpooledHeapByteBuf(ridx: 118, widx: 118, cap: 496)) at io.netty.buffer.AbstractByteBuf.ensureWritable(AbstractByteBuf.java:242) ~[netty-all-4.0.28.Final.jar:4.0.28.Final] at io.netty.buffer.AbstractByteBuf.writeLong(AbstractByteBuf.java:790) ~[netty-all-4.0.28.Final.jar:4.0.28.Final] at io.netty.buffer.WrappedByteBuf.writeLong(WrappedByteBuf.java:576) ~[netty-all-4.0.28.Final.jar:4.0.28.Final] at org.hornetq.core.buffers.impl.ChannelBufferWrapper.writeLong(ChannelBufferWrapper.java:605) ~[hornetq-commons-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.wireformat.SessionReceiveMessage.encode(SessionReceiveMessage.java:71) ~[hornetq-core-client-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.ChannelImpl.send(ChannelImpl.java:230) ~[hornetq-core-client-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBatched(ChannelImpl.java:205) ~[hornetq-core-client-2.4.3.Final.jar:na] at org.hornetq.core.protocol.core.impl.CoreSessionCallback.sendMessage(CoreSessionCallback.java:76) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:942) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:398) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:2544) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:2137) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl.access$1300(QueueImpl.java:81) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:2917) ~[hornetq-server-2.4.3.Final.jar:na] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104) [hornetq-core-client-2.4.3.Final.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60] I know this is a rather unlikely ehancement request considering that hornetq-2.4.7 actually uses netty-4.0.13. But if someone can fix this issue or at least guide me on how to fix it, I would very much appreciate it.

    JBoss Issue Tracker | 1 year ago | Andeka Putra
    java.lang.IndexOutOfBoundsException: writerIndex(117) + minWritableBytes(8) exceeds maxCapacity(118): SlicedByteBuf(ridx: 0, widx: 117, cap: 118/118, unwrapped: UnpooledHeapByteBuf(ridx: 118, widx: 118, cap: 496))
  3. 0

    hornetq 2.4 error after listner connection

    Stack Overflow | 2 months ago | Mounaim Latif
    java.lang.IndexOutOfBoundsException: writerIndex(275) + minWritableBytes(8) exceeds maxCapacity(276): SlicedAbstractByteBuf(ridx: 0, widx: 275, cap: 276/276, unwrapped: UnpooledUnsafeHeapByteBuf(ridx: 276, widx: 276, cap: 464))
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IndexOutOfBoundsException

      writerIndex(117) + minWritableBytes(8) exceeds maxCapacity(118): SlicedByteBuf(ridx: 0, widx: 117, cap: 118/118, unwrapped: UnpooledHeapByteBuf(ridx: 118, widx: 118, cap: 496))

      at io.netty.buffer.AbstractByteBuf.ensureWritable()
    2. Netty
      WrappedByteBuf.writeLong
      1. io.netty.buffer.AbstractByteBuf.ensureWritable(AbstractByteBuf.java:242)[netty-all-4.0.28.Final.jar:4.0.28.Final]
      2. io.netty.buffer.AbstractByteBuf.writeLong(AbstractByteBuf.java:790)[netty-all-4.0.28.Final.jar:4.0.28.Final]
      3. io.netty.buffer.WrappedByteBuf.writeLong(WrappedByteBuf.java:576)[netty-all-4.0.28.Final.jar:4.0.28.Final]
      3 frames
    3. HornetQ
      OrderedExecutorFactory$OrderedExecutor$1.run
      1. org.hornetq.core.buffers.impl.ChannelBufferWrapper.writeLong(ChannelBufferWrapper.java:605)[hornetq-commons-2.4.3.Final.jar:na]
      2. org.hornetq.core.protocol.core.impl.wireformat.SessionReceiveMessage.encode(SessionReceiveMessage.java:71)[hornetq-core-client-2.4.3.Final.jar:na]
      3. org.hornetq.core.protocol.core.impl.ChannelImpl.send(ChannelImpl.java:230)[hornetq-core-client-2.4.3.Final.jar:na]
      4. org.hornetq.core.protocol.core.impl.ChannelImpl.sendBatched(ChannelImpl.java:205)[hornetq-core-client-2.4.3.Final.jar:na]
      5. org.hornetq.core.protocol.core.impl.CoreSessionCallback.sendMessage(CoreSessionCallback.java:76)[hornetq-server-2.4.3.Final.jar:na]
      6. org.hornetq.core.server.impl.ServerConsumerImpl.deliverStandardMessage(ServerConsumerImpl.java:942)[hornetq-server-2.4.3.Final.jar:na]
      7. org.hornetq.core.server.impl.ServerConsumerImpl.proceedDeliver(ServerConsumerImpl.java:398)[hornetq-server-2.4.3.Final.jar:na]
      8. org.hornetq.core.server.impl.QueueImpl.proceedDeliver(QueueImpl.java:2544)[hornetq-server-2.4.3.Final.jar:na]
      9. org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:2137)[hornetq-server-2.4.3.Final.jar:na]
      10. org.hornetq.core.server.impl.QueueImpl.access$1300(QueueImpl.java:81)[hornetq-server-2.4.3.Final.jar:na]
      11. org.hornetq.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:2917)[hornetq-server-2.4.3.Final.jar:na]
      12. org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:104)[hornetq-core-client-2.4.3.Final.jar:na]
      12 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_60]
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_60]
      3. java.lang.Thread.run(Thread.java:745)[na:1.8.0_60]
      3 frames