Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-1580

m2k fails with Error publishing event ProcessInstanceDataEvent

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      Running the m2k workflow on the 1.2.0-rc9 image fails with this error in the m2k pod.

       

      2024-08-09 16:16:52,679 ERROR [org.kie.kog.add.qua.mes.com.AbstractQuarkusCloudEventEmitter] (vert.x-eventloop-thread-3) Error publishing event ProcessInstanceDataEvent {specVersion=1.0, id='88ab51c0-e055-471a-8965-ede3fb969c90', source=/process/m2k, type='save-transformation', time=2024-08-09T16:01:52.643029106Z, subject='null', dataContentType='null', dataSchema=null, data={"gitRepo":"ssh://github.com/orchestrator-test/fligth-path-test-repo.git","branch":"user:default/guest","workspaceId":"29b39758-7534-4c52-86c5-a4bb4172cb21","projectId":"d11b111a-c65d-4b4b-bf4c-6067a076f5cd","transformId":"d1375d1d-7bc5-44f6-ad7e-a97a1c525dab","workflowCallerId":"b9f7e11e-e8b6-429a-bd54-aae2bfd40bfb"}, kogitoProcessInstanceId='b9f7e11e-e8b6-429a-bd54-aae2bfd40bfb', kogitoRootProcessInstanceId='null', kogitoProcessId='m2k', kogitoRootProcessId='null', kogitoAddons='null', kogitoIdentity='null', extensionAttributes={kogitobusinesskey=375601e1-89d0-4f9b-9e6f-b5a85516bba2, kogitoproctype=SW, kogitoprocinstanceid=b9f7e11e-e...72	at io.quarkus.reactivemessaging.http.runtime.HttpSink.lambda$invoke$5(HttpSink.java:112)73	at io.smallrye.context.impl.wrappers.SlowContextualFunction.apply(SlowContextualFunction.java:21)74	at io.smallrye.mutiny.operators.uni.UniOnItemTransform$UniOnItemTransformProcessor.onItem(UniOnItemTransform.java:36)75	at io.smallrye.mutiny.vertx.AsyncResultUni.lambda$subscribe$1(AsyncResultUni.java:35)76	at io.smallrye.mutiny.vertx.DelegatingHandler.handle(DelegatingHandler.java:25)77	at io.vertx.ext.web.client.impl.HttpContext.handleDispatchResponse(HttpContext.java:397)78	at io.vertx.ext.web.client.impl.HttpContext.execute(HttpContext.java:384)79	at io.vertx.ext.web.client.impl.HttpContext.next(HttpContext.java:362)80	at io.vertx.ext.web.client.impl.HttpContext.fire(HttpContext.java:329)81	at io.vertx.ext.web.client.impl.HttpContext.dispatchResponse(HttpContext.java:291)82	at io.vertx.ext.web.client.impl.HttpContext.lambda$handleReceiveResponse$7(HttpContext.java:507)83	at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:277)84	at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:259)85	at io.vertx.core.impl.EventLoopContext.lambda$runOnContext$0(EventLoopContext.java:43)86	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)87	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)88	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)89	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566)90	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)91	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)92	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)93	at java.base/java.lang.Thread.run(Thread.java:840)94952024-08-09 16:18:11,446 WARN  [org.jbo.res.cli.jax.i18n] (Cleaner-0) RESTEASY004687: Closing a class org.jboss.resteasy.client.jaxrs.engines.ManualClosingApacheHttpClient43Engine$CleanupAction instance for you. Please close clients yourself.962024-08-09 16:37:18,446 INFO  [org.kie.kog.ser.wor.act.SysoutAction] (executor-thread-2) m2k workflow: fdddb533-0212-4832-b22c-a4d6cf40489c transformation ID: 61473a73-baf3-4e9d-8ff2-0adc91622e40 

      and this error in the move2kube pod:

       

       

      time="2024-08-09T16:38:03Z" level=error msg="failed to get the next question. Error: \"failed to send a GET request to the URL http://localhost:45431/problems/current . Error: \\\"Get \\\\\\\"http://localhost:45431/problems/current\\\\\\\": dial tcp [::1]:45431: connect: connection refused\\\"\"" request-id=36d7fd4e-14a6-4440-bf6c-0403cbae1ffc 

      full logs are attached. 

       

      How reproducible:

      100%

      Steps to reproduce:

      1. Run m2k workflow

      2. Wait for status complete

      3. Workflow is stuck in active with the above errors present in the logs

      Actual results:

      workflow doesn't complete successfully

      Expected results:

      workflow completes successfully

       

              rgolan1@redhat.com Roy Golan
              gharden1 Gary Harden
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: