Mule 4: Opentelementry upgrade from 1.2.0 to 1.5.0 results in DB connection exhaustion

[molabus2]

Our Mule 4.4 application currently employs OpenTelemetry version 1.2.0. However, upon upgrading to version 1.5.0, we encountered an issue where the application exhausts its database connections (Oracle) after handling the initial requests successfully. It appears that the database connections are not being released properly for some unknown reason. We're using mule DB Connector to call DB stored procedures (db:stored-procedure).

[manikmagar]

@molabus2 OpenTelemetry module does not use anything from any connections. It works purely based on the notifications generated by the mule runtime. I don't see any reason for opentelemetry module causing this. Do you see anything in the logs or resource (thread/cpu) consumption? Has anything else changed - runtime, dependencies, app resource configuration?

[manikmagar]

@molabus2 I forgot about one change in 1.15.0. In addition to notifications, the module uses interceptors to capture processor spans. I am not sure how to quantify "initial requests" though. Could you provide any sample app that can reproduce this? Or, provide more details on your OpenTelementry global configuration and DB flow.

[manikmagar]

I am closing this due to non-reproducibility and no activity.