Details
-
Bug
-
Resolution: Done
-
Major
-
JDG 7.1.0 ER2
-
None
Description
When the JS client puts entries into the server under the load, sometimes exception appears (with different codes):
org.infinispan.server.hotrod.HotRodUnknownOperationException: Unknown operation: 117 at org.infinispan.server.hotrod.Decoder2x.readHeader(Decoder2x.java:78) at org.infinispan.server.hotrod.HotRodDecoder.readHeader(HotRodDecoder.java:209) at org.infinispan.server.hotrod.HotRodDecoder.decodeHeader(HotRodDecoder.java:130) at org.infinispan.server.hotrod.HotRodDecoder.decode(HotRodDecoder.java:88) at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:411) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:248) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350) at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) at org.infinispan.server.core.transport.StatsChannelHandler.channelRead(StatsChannelHandler.java:28) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350) at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358) at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926) at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:972) at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:386) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:302) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) at java.lang.Thread.run(Thread.java:745)
You can find more logs e.g. here: https://jdg-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jdg-js-xsite-client-failover/41/console-edg-perf01-fc501546-4eda-4f26-b331-907a0b422709/
Due to this exception it is not possible to verify in perflab if the xsite failover takes place properly or no.
