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

Log flooded with warning if Jaeger is not running

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 25.0.0.Final
    • 25.0.0.Beta1
    • REST
    • None

    Description

      With the OpenTelemetry susbsystem configured (which it is by default), users will see warning messages flood the logs if they have a REST application deployed, but do not have the Jaeger collector running (and properly configured):

       

      15:03:07,739 WARNING [io.opentelemetry.exporter.jaeger.JaegerGrpcSpanExporter] (grpc-default-executor-1) Failed to export spans: io.grpc.StatusRuntimeException: UNAVAILABLE
          at io.grpc.Status.asRuntimeException(Status.java:535)
          at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:533)
          at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:464)
          at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:428)
          at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:461)
          at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:553)
          at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:68)
          at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:739)
          at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:718)
          at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
          at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
          at java.lang.Thread.run(Thread.java:748)
      Caused by: java.net.ConnectException: Connection refused (Connection refused)
          at java.net.PlainSocketImpl.socketConnect(Native Method)
          at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:476)
          at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:218)
          at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:200)
          at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:394)
          at java.net.Socket.connect(Socket.java:606)
          at java.net.Socket.connect(Socket.java:555)
          at java.net.Socket.<init>(Socket.java:451)
          at java.net.Socket.<init>(Socket.java:261)
          at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:277)
          at io.grpc.okhttp.OkHttpClientTransport$4.run(OkHttpClientTransport.java:556)
          ... 4 more
      

      We should probably set the log level for otel to error to suppress this behavior before WF 25 final ships

      Attachments

        Issue Links

          Activity

            People

              jaslee@redhat.com Jason Lee
              jaslee@redhat.com Jason Lee
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: