Brian Stansberry created WFLY-13820: --------------------------------------- Summary: Make the annoying jaeger 'shutdown hook' logging go away Key: WFLY-13820 URL: https://issues.redhat.com/browse/WFLY-13820 Project: WildFly Issue Type: Enhancement Components: MP OpenTracing Reporter: Brian Stansberry Assignee: Emmanuel Hugonnet If there's something simple that can be done to make this go away it would be nice. {code} INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-4) No shutdown hook registered: Please call close() manually on application shutdown. INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-2) No shutdown hook registered: Please call close() manually on application shutdown. {code} I'm not looking for anything nasty or complex here; feel free to reject this if something like that is needed. Of course if what's it's asking for is something we should be doing but aren't, then this is a bug. :) But I assume whatever it would want done via a shutdown hook is not something an appserver that supports 'reload' would use a shutdown hook to accomplish. -- This message was sent by Atlassian Jira (v7.13.8#713008)