Our .Net webservice provides data for about 1000 users and 3000 request per seconds.
If it connects to a database reside on LAN, every thing is OK. But when it connects to a database through The Internet, and naturally, connection will some times not stable and it lead to dead connections. In client's connection pool, connections are still there and on the server also but they are dead already. No connection will be created after that because of full connection pool.
If that happend, we have to reset IIS :( and it happens a lot.
We are using free version of DotConnect 7.3.132.0, Oracle 10g and webservice written in .Net 2.0.
Please help :(
Asked
Active
Viewed 89 times
0
QuangND
- 97
- 1
- 12
-
Does dead client detection help here? – Feb 21 '14 at 08:40
-
I do not understand your question. I try to ClearPool but no luck :( – QuangND Feb 21 '14 at 10:26
-
speak to your dba and check the Dead Client Detection settings in the sqlnet.ora on the rdbms server host. I am not sure, it could help. – Feb 21 '14 at 13:23
-
DB is ok with dead connections, problems are on client side. – QuangND Feb 23 '14 at 07:09