Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14650

Warn message SRMSG18216: No `group.id` set during microprofile-reactive-messaging-kafka QS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 23.0.1.Final
    • 23.0.0.Final
    • Quickstarts
    • None
    • Hide
      1. unzip WildFly server
      2. ./bin/standalone.sh
      3. enable reactive messaging via CLI:
        batch
        /extension=org.wildfly.extension.microprofile.reactive-messaging-smallrye:add
        /extension=org.wildfly.extension.microprofile.reactive-streams-operators-smallrye:add
        /subsystem=microprofile-reactive-streams-operators-smallrye:add
        /subsystem=microprofile-reactive-messaging-smallrye:add
        run-batch
        reload
        
      4. get quickstart code:
        git clone git@github.com:wildfly/quickstart.git -b 23.0.0.Final
        cd quickstart/microprofile-reactive-messaging-kafka
        
      5. run quickstart test via
        mvn clean verify -Parq-remote
        
      6. see mentioned warning in WildFly server logs
      Show
      unzip WildFly server ./bin/standalone.sh enable reactive messaging via CLI: batch /extension=org.wildfly.extension.microprofile.reactive-messaging-smallrye:add /extension=org.wildfly.extension.microprofile.reactive-streams-operators-smallrye:add /subsystem=microprofile-reactive-streams-operators-smallrye:add /subsystem=microprofile-reactive-messaging-smallrye:add run-batch reload get quickstart code: git clone git@github.com:wildfly/quickstart.git -b 23.0.0.Final cd quickstart/microprofile-reactive-messaging-kafka run quickstart test via mvn clean verify -Parq-remote see mentioned warning in WildFly server logs
    • Undefined

      I can see following warning when I run WildFly microprofile-reactive-messaging-kafka quickstart:

      09:52:33,893 WARN  [io.smallrye.reactive.messaging.kafka] (MSC service thread 1-4) SRMSG18216: No `group.id` set in the configuration, generate a random id: cc39193b-b30b-4d3a-887f-ff24894569a1
      

      We should try to avoid any warning messages during the QS execution, if applicable.

            kkhan1@redhat.com Kabir Khan
            jstourac@redhat.com Jan Stourac
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: