search

avioconsulting / mule-opentelemetry-module

Mule Extension to generate OpenTelemetry traces and metrics
https://avioconsulting.github.io/mule-opentelemetry-module/
BSD 2-Clause "Simplified" License
23 stars 8 forks source link

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

Open molabus2 opened 6 months ago

molabus2 commented 6 months ago

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 commented 6 months ago

@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 commented 6 months ago

@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.