Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-7401

Breaking change in SW tests and maybe other too

    XMLWordPrintable

Details

    • False
    • None
    • False
    • ---
    • ---
    • 2022 Week 23-25 (from Jun 6)

    Description

      Guys, cnicolai@redhat.com , nmirasch@redhat.com ,

      this commit  https://github.com/kiegroup/kogito-runtimes/commit/723bf7356cefb0f39f708c6bdf5326bd8b5a8c71

       

      Is breaking the SW native integration tests.

       

      If you rollback to the commit before: https://github.com/kiegroup/kogito-runtimes/commit/0fa3fbca983fb5fe4e5ea2df3e401f04c0cb1aaf

      and you build the project, and execute the SW integration tests again with mvn clean install -Pnative, the tests works again.

       

      However with the commit I've mentioned the test doesn't work because the kogito generated application is broken.

       

      2022-06-17 16:20:21,575 DEBUG [org.kie.kog.per.jdb.GenericRepository] (main) Found process_instance table
      2022-06-17 16:20:21,579 DEBUG [org.kie.kog.per.jdb.GenericRepository] (main) Found process_instance table
      2022-06-17 16:20:21,591 ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): javax.enterprise.inject.spi.DefinitionException: SRMSG00019: Unable to connect an emitter with the channel `kogito_outgoing_stream`
          at io.smallrye.reactive.messaging.providers.extension.ChannelProducer.getEmitter(ChannelProducer.java:187)
          at io.smallrye.reactive.messaging.providers.extension.ChannelProducer.produceEmitter(ChannelProducer.java:136)
          at io.smallrye.reactive.messaging.providers.extension.ChannelProducer_ProducerMethod_produceEmitter_86c8bb1e4975aaf33dff96bec0d2fc8fa44920ab_Bean.create(Unknown Source)
          at io.smallrye.reactive.messaging.providers.extension.ChannelProducer_ProducerMethod_produceEmitter_86c8bb1e4975aaf33dff96bec0d2fc8fa44920ab_Bean.get(Unknown Source)
          at io.smallrye.reactive.messaging.providers.extension.ChannelProducer_ProducerMethod_produceEmitter_86c8bb1e4975aaf33dff96bec0d2fc8fa44920ab_Bean.get(Unknown Source)
          at io.quarkus.arc.impl.CurrentInjectionPointProvider.get(CurrentInjectionPointProvider.java:60)
          at org.kie.kogito.app.Kogito_outgoing_streamEventEmitter_Bean.create(Unknown Source)
          at org.kie.kogito.app.Kogito_outgoing_streamEventEmitter_Bean.create(Unknown Source)
          at io.quarkus.arc.impl.AbstractSharedContext.createInstanceHandle(AbstractSharedContext.java:111)
          at io.quarkus.arc.impl.AbstractSharedContext$1.get(AbstractSharedContext.java:35)
          at io.quarkus.arc.impl.AbstractSharedContext$1.get(AbstractSharedContext.java:32)
          at io.quarkus.arc.impl.LazyValue.get(LazyValue.java:26)
          at io.quarkus.arc.impl.ComputingCache.computeIfAbsent(ComputingCache.java:69)
          at io.quarkus.arc.impl.AbstractSharedContext.get(AbstractSharedContext.java:32)
          at io.quarkus.arc.impl.ClientProxies.getApplicationScopedDelegate(ClientProxies.java:19)
          at org.kie.kogito.app.Kogito_outgoing_streamEventEmitter_ClientProxy.arc$delegate(Unknown Source)
          at org.kie.kogito.app.Kogito_outgoing_streamEventEmitter_ClientProxy.arc_contextualInstance(Unknown Source)
          at org.kie.kogito.app.Kogito_outgoing_streamEventEmitter_Observer_Synthetic_d70cd75bf32ab6598217b9a64a8473d65e248c05.notify(Unknown Source)
          at io.quarkus.arc.impl.EventImpl$Notifier.notifyObservers(EventImpl.java:323)
          at io.quarkus.arc.impl.EventImpl$Notifier.notify(EventImpl.java:305)
          at io.quarkus.arc.impl.EventImpl.fire(EventImpl.java:73)

       

      Details here:

      https://gist.github.com/wmedvede/6f93f519131f7a9663552cd91ecc1ee6

       

      I believe that this will affect all the SW that works with messages/events since, something is going wrong when the kogito observer is being instantiated.

       

      Wondering if this dependency that was added for the process tests is required now for the SW

      <dependency>      <groupId>io.quarkiverse.reactivemessaging.http</groupId>      <artifactId>quarkus-reactive-messaging-http</artifactId>    </dependency> 

      Would you mind take a look?

       

      Thanks!

       

       

       

       

      Attachments

        Activity

          People

            nmirasch@redhat.com Neus Miras Chueca
            wmedvede@redhat.com Walter Medvedeo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: