You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
I use an oracle datasource to call a storedProcedure in oracle database. After some traffic we wait long enough for the connections to be evicted from the pool. However, the connections stay open resulting in oom in db eventually.
This is related to #6078 . However, in this issue the oracle datasource is not transacted. Although i tried making it transacted with narayana result did not change.
// On the other hand, oracle ds did not work with btm.(I wanted to test with btm since it is more stable than narayana atm.)
Apparently, btm+oracle works when oracle is non-xa
I tried setting connectionsArePooled="false" in sender but that did not help. Maybe that setting is no longer works.
Or we leak some resource(stmt, rs) in the framework that keeps the connection open in definitely...
Reporter
Ali
FF: 7.9-RC1-hotfix10
The text was updated successfully, but these errors were encountered:
❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
I use an oracle datasource to call a storedProcedure in oracle database. After some traffic we wait long enough for the connections to be evicted from the pool. However, the connections stay open resulting in oom in db eventually.
This is related to #6078 . However, in this issue the oracle datasource is not transacted. Although i tried making it transacted with narayana result did not change.
// On the other hand, oracle ds did not work with btm.(I wanted to test with btm since it is more stable than narayana atm.)
Apparently, btm+oracle works when oracle is non-xa
I tried setting connectionsArePooled="false" in sender but that did not help. Maybe that setting is no longer works.
Or we leak some resource(stmt, rs) in the framework that keeps the connection open in definitely...
Reporter
Ali
FF: 7.9-RC1-hotfix10
The text was updated successfully, but these errors were encountered: