Loïc Mathieu

@radcortez if we plan to drop support for Quarkus so OK for me to move the current MongoDB support from OpenTracing to OpenTelemetry. There is a command listener used to...

@radcortez these are based on a Java agent which is a different strategy that should not need anything on our side but as it required JVMTI will not work in...

It also uses a command listener so we may be able to use it like we did for OpenTracing, I don't know why it is for 3.1 maybe it can...

Fixed by #40191

> potentially through a Quarkus-specific facade. this will be a lot of work as the transactonal facade will need to be kepts in line with the underlying MongoDB 'raw' facilities....

@languitar currently, the ClientSession is created lazilly at first use and registered inside the transaction manager. Then we reuse the existing transaction interceptors. So it may be hard to provide...

@yrodiere just saw it has been released upstream and I rebase an old prototype I made years ago (to base an hypotetical Elasticsearch with Panache extension on it, see https://groups.google.com/g/quarkus-dev/c/pDQJ_yRNML4/m/UjCwseXXAwAJ)....

@yrodiere yes, it was preliminary work for Elasticsearch with Panache but no "panache" stuff was done, I'll rename it. And yes, native has not been tested yet. We'll revisit it...

I don't know if it is of any help but I notice on an heap dump that it appears that in the `DelayedExecutionFlowImpl` there is a head attribute which contains...

cc @yawkat