-
1. Re: [io.jaegertracing.internal.JaegerTracer#<init>] No shutdown hook registered: Please call close() manually on application shutdown.
The tracers configured in the subsystem and injected from Jaeger by WildFly are using manualShutdown. Are you using a environment variable tracer ?
wildfly/JaegerTracerConfiguration.java at master · wildfly/wildfly · GitHub
-
2. Re: [io.jaegertracing.internal.JaegerTracer#<init>] No shutdown hook registered: Please call close() manually on application shutdown.
No, no such environment variable.
The WildFly server 19.x is running on a Solaris SPARC Server, not in a cloud environment or a container.
As this currently is and possibly will be the deployment situation for our customers, I for now slimmed down the standalone-full.xml and eliminated all microprofile modules.
-
3. Re: [io.jaegertracing.internal.JaegerTracer#<init>] No shutdown hook registered: Please call close() manually on application shutdown.
As this is a pure jaeger client trace we could switch to WARN this category.
-
4. Re: [io.jaegertracing.internal.JaegerTracer#<init>] No shutdown hook registered: Please call close() manually on application shutdown.
In conclusion looking at jaeger client code this is not an issue at all and this is not a warning. Just an info that a tracer lifecycle is managed by WildFly (looking at the code you can see that this is also the case for glassfish)