java.lang.IndexOutOfBoundsException

Exception #2577015

Samebug tips0

We couldn't find tips for this exception.

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

Stack trace

  • java.lang.IndexOutOfBoundsException at com.tangosol.io.nio.ByteBufferWriteBuffer.write(ByteBufferWriteBuffer.java:109) at com.tangosol.io.AbstractWriteBuffer$AbstractBufferOutput.write(AbstractWriteBuffer.java:536) at com.tangosol.io.MultiBufferWriteBuffer$MultiBufferOutput.write(MultiBufferWriteBuffer.java:512) at com.tangosol.io.WrapperBufferOutput.write(WrapperBufferOutput.java:71) at com.tangosol.io.WrapperDataOutputStream.write(WrapperDataOutputStream.java:135) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1877) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1786) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1189) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) at com.tangosol.util.ExternalizableHelper.writeSerializable(ExternalizableHelper.java:2485) at com.tangosol.util.ExternalizableHelper.writeObject(ExternalizableHelper.java:2688) at com.tangosol.coherence.component.net.management.model.localModel.WrapperModel.writeExternal(WrapperModel.CDB:51) at com.tangosol.util.ExternalizableHelper.writeExternalizableLite(ExternalizableHelper.java:2294) at com.tangosol.util.ExternalizableHelper.writeObject(ExternalizableHelper.java:2684) at com.tangosol.coherence.component.net.management.Connector$Register.writeExternal(Connector.CDB:15) at com.tangosol.util.ExternalizableHelper.writeExternalizableLite(ExternalizableHelper.java:2294) at com.tangosol.util.ExternalizableHelper.writeObject(ExternalizableHelper.java:2684) at com.tangosol.io.DefaultSerializer.serialize(DefaultSerializer.java:47) at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.writeObject(Service.CDB:1) at com.tangosol.coherence.component.net.Message.writeObject(Message.CDB:1) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationMessage.write(InvocationService.CDB:3) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.serializeMessage(Grid.CDB:21) at com.tangosol.coherence.component.net.MessageHandler.serializeMessage(MessageHandler.CDB:19) at com.tangosol.coherence.component.net.MessageHandler.post(MessageHandler.CDB:36) at com.tangosol.coherence.component.net.Message.dispatch(Message.CDB:76) at com.tangosol.coherence.component.net.Message.post(Message.CDB:1) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.post(Grid.CDB:2) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.send(Grid.CDB:1) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.execute(InvocationService.CDB:39) at com.tangosol.coherence.component.util.safeService.SafeInvocationService.execute(SafeInvocationService.CDB:1) at com.tangosol.coherence.component.net.management.Connector.sendRegister(Connector.CDB:19) at com.tangosol.coherence.component.net.management.Connector.registerAll(Connector.CDB:8) at com.tangosol.coherence.component.net.management.Connector.onAnnouncement(Connector.CDB:10) at com.tangosol.coherence.component.net.management.Connector$Announce.run(Connector.CDB:2) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.onInvocationRequest(InvocationService.CDB:16) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationRequest.onReceived(InvocationService.CDB:40) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:38) at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:23) at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:54) at java.lang.Thread.run(Thread.java:745)

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

We couldn't find other users who have seen this exception.