Bump opentracing-jdbc.version from 0.2.4 to 0.2.11

[clockworkorange]

Bump opentracing-jdbc.version from 0.2.4 to 0.2.11 to avoid java.lang.IllegalStateException: Timer already cancelled. with tracing and Oracle database.

java-jdbc issue: opentracing-contrib/java-jdbc#73

[gsmet]

Unfortunately, we cannot do that because of: #18033 . We have been bugging upstream for a while but they didn't answer to any of our questions/requests so we're kinda stuck.

Also see:

• Not compatible with native image since version 0.2.5 opentracing-contrib/java-jdbc#116
• Patch Classes.getAllInterfaces to return predictable array opentracing-contrib/java-common#2

[gsmet]

See my comment. We cannot merge that, unfortunately.

[gsmet]

@radcortez do you have any contacts with the OpenTracing people? It would be really nice if we could find a solution to this issue.

The issue is where we have the problem explained the best: opentracing-contrib/java-jdbc#116

[radcortez]

@radcortez do you have any contacts with the OpenTracing people? It would be really nice if we could find a solution to this issue.

I have on the OpenTelemetry community (some came from OpenTracing), so I can ask around. I won't keep my hopes up, since OpenTracing was completely abandoned, and some of the projects in the https://github.com/opentracing-contrib organization were maintained by external contributors (not sure about opentracing-jdbc).

I'm having a similar issue with some other projects in that organization, because of the jakarta namespace rename. I've just decided to copy the code and do the required modifications, so we may need to do something similar here.