APIM Micro-gateway 3.2.0 trigger errors when starting the server with jaeger tracing configurations enabled

[riyazathali]

Description:

Microgateway APIM 3.2.0 is started with the error log when the following tracing configurations are enabled in the micro-gw.conf of the MGW runtime.

[b7a.observability.tracing]
enabled=true
name="jaeger"
[b7a.observability.tracing.jaeger.sampler]
type="const"
param=1.0
[b7a.observability.tracing.jaeger.reporter]
hostname="localhost"
port=5775
[b7a.observability.tracing.jaeger.reporter.flush.interval]
ms=2000
[b7a.observability.tracing.jaeger.reporter.max.buffer]
spans=1000

Error is as below.

[ballerina/http] started HTTP/WS listener 0.0.0.0:9797
ballerina: started Prometheus HTTP listener 0.0.0.0:9797
ballerina: started publishing tracers to Jaeger on jaeger-agent.applications:5775
error: error getting tracer for jaeger. org.apache.thrift.transport.AutoExpandingBufferWriteTransport.<init>(ID)V
ballerina: Oh no, something really went wrong.

The `ballerina-internal.log` file located in the current directory
will indicate what the problem is.
We really appreciate it if you can share with us, the code
that broke Ballerina, together with this log file by creating a
bug report in https://github.com/ballerina-platform/ballerina-lang/issues.

Steps to reproduce:

1. Build the MGW project jar via API micro gateway 3.2.0 (Update level 6)
2. Run the jar via micro gateway runtime 3.2.3

Affected Product Version:

API micro gateway toolkit 3.2.0
API micro gateway runtime 3.2.3