J
jabailo
Platform:
W2K
IIS 5.0
..NET 1.1
ADO.NET managed DB2 provider for iSeries
I wrote a web service which allows me to post records to the as/400
Occasionally there seem to be errors such as "Communication Problem".
I believe these are related to the connection pool.
We reboot our as/400 every week, and I think this is leaving the
connections in a hanging state.
As a way around that, I tried implementing the static method :
IBM.Data.DB2.iSeries.iDB2Connection.CleanupPooledConnections();
But once that command is executed, I am no longer allowed to create a
iDB2Connection -- it seems to *nuke* every thing. It is sortof
expected as in the documentation they say to execute it only after the
app is closed. However, a web service never really /closes/ once it's
been started. With my web service, the only way I can connect after
that command is to restart my aspnet_wp.exe process from task manager.
This is also the way (other than rebooting the server) to recover
from the problem described above.
Question: Is there a way to clean up pooled connections from a web
service without having to restart the aspnet worker process?
W2K
IIS 5.0
..NET 1.1
ADO.NET managed DB2 provider for iSeries
I wrote a web service which allows me to post records to the as/400
Occasionally there seem to be errors such as "Communication Problem".
I believe these are related to the connection pool.
We reboot our as/400 every week, and I think this is leaving the
connections in a hanging state.
As a way around that, I tried implementing the static method :
IBM.Data.DB2.iSeries.iDB2Connection.CleanupPooledConnections();
But once that command is executed, I am no longer allowed to create a
iDB2Connection -- it seems to *nuke* every thing. It is sortof
expected as in the documentation they say to execute it only after the
app is closed. However, a web service never really /closes/ once it's
been started. With my web service, the only way I can connect after
that command is to restart my aspnet_wp.exe process from task manager.
This is also the way (other than rebooting the server) to recover
from the problem described above.
Question: Is there a way to clean up pooled connections from a web
service without having to restart the aspnet worker process?