Thanks for the question, Tomáš .
Asked: July 13, 2022 - 9:51 pm UTC
Last updated: August 10, 2022 - 3:17 am UTC
Version: 11.2
Viewed 1000+ times
You Asked
Hello,
We have issue since we have moved from entity framework 6 on .net 48 to entity framework core on net 6.
The thing is, that after any kind of application termination, there are processes left open, alongside sessions, which result slowly creeping up to limmit and throwing maximum number of sessions exceeded.
Is there any way to properly terminate entity framework core to notify and kill those processes?
Thanks,
Developer
and Connor said...
Thanks for your patience - this one slipped through the cracks.
Check out Dead Connection detection which should help clean up dead sessions if they are not being cleaned up properly by the application
https://www.oracle.com/technetwork/database/enterprise-edition/oraclenetdcd-2179641.pdf Other options (can be additional to the above) are:
a) would be to set an idle timeout in a profile so that sessions that are left hanging around are eventually sniped by the database to free up any resources they might be holding
b) once you get to a supported database release (19c) set "max_idle_blocker_time" to stop any old sessions holding locks that might block others