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

Warn message 'Failed to flush spans' during microprofile-reactive-messaging-kafka QS

    XMLWordPrintable

Details

    • 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 warnings 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 warnings in WildFly server logs
    • Undefined

    Description

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

      09:52:36,446 WARN  [io.jaegertracing.internal.reporters.RemoteReporter] (jaeger.RemoteReporter-QueueProcessor) FlushCommand execution failed! Repeated errors of this command will not be logged.: io.jaegertracing.internal.exceptions.SenderException: Failed to flush spans.
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.ThriftSender.flush(ThriftSender.java:115)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.internal.reporters.RemoteReporter$FlushCommand.execute(RemoteReporter.java:160)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.internal.reporters.RemoteReporter$QueueProcessor.run(RemoteReporter.java:182)
        at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: io.jaegertracing.internal.exceptions.SenderException: Could not send 1 spans
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.UdpSender.send(UdpSender.java:85)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.ThriftSender.flush(ThriftSender.java:113)
        ... 3 more
Caused by: org.apache.thrift.transport.TTransportException: Cannot flush closed transport
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.reporters.protocols.ThriftUdpTransport.flush(ThriftUdpTransport.java:148)
        at org.apache.thrift@0.13.0//org.apache.thrift.TServiceClient.sendBase(TServiceClient.java:73)
        at org.apache.thrift@0.13.0//org.apache.thrift.TServiceClient.sendBaseOneway(TServiceClient.java:66)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.agent.thrift.Agent$Client.send_emitBatch(Agent.java:70)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.agent.thrift.Agent$Client.emitBatch(Agent.java:63)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.senders.UdpSender.send(UdpSender.java:83)
        ... 4 more
Caused by: java.net.PortUnreachableException: ICMP Port Unreachable
        at java.base/java.net.PlainDatagramSocketImpl.send(Native Method)
        at java.base/java.net.DatagramSocket.send(DatagramSocket.java:695)
        at io.jaegertracing.jaeger@1.5.0//io.jaegertracing.thrift.internal.reporters.protocols.ThriftUdpTransport.flush(ThriftUdpTransport.java:146)
        ... 9 more

      This warning seems to be more related with MP OpenTracing than with MP Reactive Messaging. Although, something in the QS is triggering it to occur.

      The warning message is (quite obviously) not present when the `microprofile-opentracing-smallrye` subsystem is removed:

      /subsystem=microprofile-opentracing-smallrye:remove()
reload

      So, it looks like OpenTracing feature seems to be triggered by this QS code and since there is not configured any Jaeger agent/collector, the flush operation over the spans simply fails.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-14625 WARN message jaegertracing: FlushCommand execution failed!

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: