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

Opentracing is not working after redeployment

XMLWordPrintable

    • Hide
      • start Jaeger
        • docker run --rm --name jaeger -p6831:6831/udp -p16686:16686 jaegertracing/all-in-one:1.16.0
      • start WFLY – bin/standalone.sh
      • deploy the reproducer – mvn clean package wildfly:deploy
      • invoke a few times the endpoint
        • http :8080/wildfly-opentracing/hello/traced
        • see the collected spans in the Jaeger console
      • redeploy the application again – mvn clean package wildfly:deploy
      • the repeated calls to http :8080/wildfly-opentracing/hello/traced are now not being collected
      • restart the Wfly server again
      • the spans are again being collected correctly
      Show
      start Jaeger docker run --rm --name jaeger -p6831:6831/udp -p16686:16686 jaegertracing/all-in-one:1.16.0 start WFLY – bin/standalone.sh deploy the reproducer – mvn clean package wildfly:deploy invoke a few times the endpoint http :8080/wildfly-opentracing/hello/traced see the collected spans in the Jaeger console redeploy the application again – mvn clean package wildfly:deploy the repeated calls to http :8080/wildfly-opentracing/hello/traced are now not being collected restart the Wfly server again the spans are again being collected correctly

      When the application that uses opentracing is redeployment the spans are no longer sent to the Jaeger. When the server is restarted, everything works again. Please see the attached reproducer – https://github.com/xstefank/reproducers/tree/master/wildfly-opentracing

              ehugonne1@redhat.com Emmanuel Hugonnet
              mstefank Martin Stefanko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: