Wildfly 23.0.0 Final - Jaeger showing FlushCommand execution failed

Sascha Dechert

unread,

Mar 25, 2021, 1:02:00 PM3/25/21

to WildFly

Hi all,

I switched from Wildfly 15 to Wildfly 23 and my application is up and running. But very often Wildfly logs the attached warning. As an extended online search did not lead me to a solution how to get rid of jaeger completly or at least fix the warning, I hope someone can point me in the right direction over here.

Thanks in advance.

Sascha

jaeger-warning.log

James Perkins

unread,

Mar 25, 2021, 1:03:55 PM3/25/21

to WildFly

Hello Sascha,

This is being worked on right now https://issues.redhat.com/browse/WFLY-14625. As I understand it there was a change in the Jaeger Client which leads to this. It's more a nuisance than an actual issue though.

Sascha Dechert

unread,

Mar 26, 2021, 3:21:17 AM3/26/21

to WildFly

Thanks for pointing me to the right direction. Over there in the Redhat issue is a comment from David Everly that made the WARN message go away:

If you don't use it, you can do something like the following in the CLI:

/subsystem=microprofile-opentracing-smallrye/jaeger-tracer=jaeger:write-attribute(name=sampler-param, value=0)

Reply all

Reply to author

Forward