- 
        1. Re: [io.jaegertracing.internal.JaegerTracer#<init>] No shutdown hook registered: Please call close() manually on application shutdown.ehugonnet Feb 20, 2020 7:48 AM (in response to lafr)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.lafr Feb 21, 2020 1:43 PM (in response to ehugonnet)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.ehugonnet Feb 22, 2020 6:31 AM (in response to lafr)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.ehugonnet Feb 24, 2020 3:38 AM (in response to lafr)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) 
 
    