Skip to content
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.

Testcontainer query does not work with current jaeger  #64

Open
@hacst

Description

Describe the bug
Trying to establish a gRPC connection to 16686 fails with the current jaegertracing/all-in-one:1.24.0 as it is not http2 and presumably not gRPC. As documented in https://www.jaegertracing.io/docs/1.24/deployment/#query-service--ui gRPC query functionality is on port 16685 instead of 16686.

I created a patch at hacst@7749594 (untested right now) but I'm unsure how involved this would be to get landed.

To Reproduce
Steps to reproduce the behavior:

Any operation on the QueryServiceBlockingStub which initiates a request will fail with a failure to establish the underlying HTTP2 channel:

JaegerAllInOne jaeger = new JaegerAllInOne("jaegertracing/all-in-one:1.24.0")
jaeger.start();
jaeger.createBlockingQueryService().findTraces(...)

Expected behavior
Query completes without any connectivity issues

Version (please complete the following information):

  • io.jaegertracing:jaeger-testcontainers:0.7.0
  • jaegertracing/all-in-one:1.24.0

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions