October 3, 2002 at 12:28 pm
I've got over 1100 SPIDS that a I know were caused by bad ConnClose() asp fn. Is there a way to clean them up without a SQL restart? I know about the KILL fn but am wary because I've had problems using it in the past.
October 3, 2002 at 5:50 pm
If I remember correctly they should eventually time out when the sessions expire. If they are not then are you creating the at the application scope of IIS or the session? Try bouncing IIS first as well, this sometimes clear things up as the connections are generally pooled in IIS. Otherwise, yes your best bet is to stop SQL.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
October 4, 2002 at 2:42 pm
Thanks for the reply antares686. The conns are loaded into a public var, not into a session or app var. I think it may have something to do with our ISP. They are using teamed nics which are generating multiple unique network addresses for the same host and for unknown reasons the SPIDS are hanging around. Am I barking up the right tree? Here is a sample of our include.asp
Public conn
Public DB_SVR, DB_NAME, USER, PSWD, SQL_CONNECT
sub openConn()
closeConn
SQL_CONNECT = "Driver={SQL Server};Server=" & DB_SVR &";UID=" & USER &";PWD=" & PSWD &";Database=" & DB_NAME &";DNS=;"
set conn=server.CreateObject("adodb.connection")
conn.Provider="MSDataShape"
conn.Open SQL_CONNECT
end sub
sub closeConn()
on error resume next
conn.close
set conn = nothing
end sub
October 4, 2002 at 6:37 pm
First the teamed NICs should not be the cause as it should just be a total packet processing thing, connection should not open multiple times. Now as for closing I do not run into issues as long as I close the recordset and set it to nothing. Also, I only close the connection but not set to nothing so that pooling can work, makes connection opening much faster. I don't see anything that may be the root cause unless by setting = to nothing the pooling is still in effect on the server but not within IIS and thus creates a new connection, if that is the case then the pooled connections will have to timeout to diconnect and may be the problem, just give it a test and see what happens. This of course is theory on my part.
Now I am personally curious about using the MSDataShape provider? What are you doing with it? I have not seen it used in this manner.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply