Hello,
I'm having an issue with pending idle connection that's driving me crazy.
In most cases, the connections are closed after the pages of my web app are requested, but at the end of the day, I have about 130 pending idle connections that if not killed by our network administrator, drive to error of max connections exceeded.
I'm using Devart dotConnect with Entity Framework from dotNet 2010 and Postgresql 8.3.10
My connection string:
"metadata=res://*/Bonus.Entity.csdl|res://*/Bonus.Entity.ssdl|res://*/Bonus.Entity.msl;provider=Devart.Data.PostgreSql;provider connection string=\"User Id=user1234;Password=mypwd;Host=192.168.0.22;Port=5432;Database=mydb;Persist Security Info=True;Schema=public;Unicode=true\""
Idle connections persist after days
-
- Posts: 3
- Joined: Thu 03 Nov 2011 18:16
- Location: Brasil
1. Tell us the exact (x.xx.xxx) version of your dotConnect for PostgreSQL. You can find it in the Tools > PostgreSQL > About menu of Visual Studio. Does the problem persist with the latest (5.50.237) version of our provider?
2. Please send us a small test project with the corresponding DDL/DML script to reproduce the issue in our environment.
3. Try setting the "Pooling=false;" connection string parameter. Does it help?
2. Please send us a small test project with the corresponding DDL/DML script to reproduce the issue in our environment.
3. Try setting the "Pooling=false;" connection string parameter. Does it help?
-
- Posts: 3
- Joined: Thu 03 Nov 2011 18:16
- Location: Brasil
-
- Posts: 3
- Joined: Thu 03 Nov 2011 18:16
- Location: Brasil