Kogito Operator - Data Index failing

31 views
Skip to first unread message

Graeme Colman

unread,
Apr 10, 2021, 5:55:47 AMApr 10
to Kogito development mailing list
Hi all

I'm following the latest docs for running the travel agency demo on OpenShift but failing to get the operator infra running. The Data-Index is failing to start due to the error below (full pod log attached).

I'm not doing anything other than creating the Infinispan, Kafka and data-index components (tried via the kogito cli and OpenShift console) strictly following the latest docs.

What am I missing?

Many thanks! 
Graeme


2021-04-10 09:30:23,182 WARN [io.qua.config] (main) Unrecognized configuration key "quarkus.kafka.bootstrap-servers" was provided; it will be ignored; verify that the dependency extension for this configuration is set or you did not make a typo ANTLR Tool version 4.7.2 used for code generation does not match the current runtime version 4.8ANTLR Runtime version 4.7.2 used for parser compilation does not match the current runtime version 4.8ANTLR Tool version 4.7.2 used for code generation does not match the current runtime version 4.8ANTLR Runtime version 4.7.2 used for parser compilation does not match the current runtime version 4.82021-04-10 09:30:24,253 INFO [io.sma.rea.mes.kafka] (main) SRMSG18229: Configured topics for channel 'kogito-usertaskdomain-events': [kogito-usertaskinstances-events]

...

2021-04-10 09:30:24,937 INFO [org.inf.HOTROD] (main) ISPN004021: Infinispan version: Infinispan 'Corona Extra' 11.0.8.Final 2021-04-10 09:30:25,031 ERROR [org.inf.HOTROD] (HotRod-client-async-pool-1-1) ISPN004007: Exception encountered. Retry 10 out of 10: org.infinispan.client.hotrod.exceptions.TransportException:: org.infinispan.client.hotrod.exceptions.TransportException:: ISPN004071: Connection to kogito-infinispan/172.30.241.115:11222 was closed while waiting for response. at org.infinispan.client.hotrod.impl.transport.netty.ActivationHandler.exceptionCaught(ActivationHandler.java:53) at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:302) at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:281) at io.netty.channel.AbstractChannelHandlerContext.fireExceptionCaught(AbstractChannelHandlerContext.java:273) at io.netty.channel.DefaultChannelPipeline$HeadContext.exceptionCaught(DefaultChannelPipeline.java:1377) at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:302) at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:281) at io.netty.channel.DefaultChannelPipeline.fireExceptionCaught(DefaultChannelPipeline.java:907) at org.infinispan.client.hotrod.impl.transport.netty.AuthHandler.lambda$channelActive$2(AuthHandler.java:87) at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:986) at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:970) at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.channelInactive(HotRodOperation.java:110) at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.channelInactive(HeaderDecoder.java:228) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248) at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241) at io.netty.channel.ChannelInboundHandlerAdapter.channelInactive(ChannelInboundHandlerAdapter.java:81) at io.netty.handler.timeout.IdleStateHandler.channelInactive(IdleStateHandler.java:277) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248) at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241) at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248) at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901) at io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:818) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: org.infinispan.client.hotrod.exceptions.TransportException:: ISPN004071: Connection to kogito-infinispan/172.30.241.115:11222 was closed while waiting for response. ... 23 more
DataIndexPod.log

Tristan Radisson

unread,
Apr 12, 2021, 3:06:39 AMApr 12
to Kogito development mailing list
Hi Graeme,

It seems the Data-Index cannot connect to the Infinispan.
Which version of Infinispan did you install?

For now, we only support 2.0.x channel in OperatorHub (Infinispan 11 as we are still using Quarkus 1.11). See https://github.com/kiegroup/kogito-operator#kogito-operator-tested-integrations.
This is something we should add in the Kogito documentation.

FYI, upgrade of the runtimes to Quarkus 1.13.0 should happen in the next few weeks and with that, it should work with 2.1.x channel on OperatorHub (Infinispan 12.0).

Regards,

Tristan Radisson

Senior Software Quality Engineer

Business Automation Cloud

Red Hat France

trad...@redhat.com   




--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/6893bd30-39e7-485b-9b5c-d7615916a251n%40googlegroups.com.

Graeme Colman

unread,
Apr 12, 2021, 3:58:40 AMApr 12
to kogito-de...@googlegroups.com
Thank you once again Tristan!

I was using the 2.1 version of the infinispan operator, is fine with 2.0

Kind regards
Graeme



Graeme Colman
UKI Domain Solution Architect & Developer Advocacy Lead
Red Hat UK Ltd, 200 Fowler Avenue, Farnborough, Hampshire, GU14 7JP



You received this message because you are subscribed to a topic in the Google Groups "Kogito development mailing list" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kogito-development/ARyvhSNCKDM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kogito-developm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kogito-development/CACsW2Z%2BuTt%2Bccm2HV4-jsQwk1uL6uz%2BNh_kbzyv0LbFFAmR6_w%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages