Help with connection pooling - connections get closed but remain active

[caroh]

Can anyone see whats wrong with this code:

The connections are remaining live in the database: and causing
"Timeout expired. The timeout period elapsed prior to obtaining a
connection from the pool" errors.

Try
'open the connection
myConnection.Op en()
'run the query
myCommand.Execu teNonQuery()
Catch ex As SqlException

Finally
'close connection
myConnection.Cl ose()

End Try

'Check to see if the service is restricted
If
myCommand.Param eters("@AccessR estrictionsSupp orted").Value.E quals(1)
Then
Return True 'service is restricted
'myConnection.C lose()
Else
Return False 'service not restricted
'myConnection.C lose()
End If

myConnection.Cl ose()

Any help/suggestions very much appreciated

Thanks!!

[Gabriel Lozano-Morán]

close the connection immediatly after the ExecuteNonQuery () method call. You
don't need the myConnection.Cl ose() at the bottom since the finally block
will always be executed. When you close a connection it returns to the
connection pool where it will be destroyed after an idle period of 4 to 7.5
minutes.

Where do you exactly get the time-outs?

Gabriel Lozano-Morán

<ca***@orange.n et> wrote in message
news:11******** *************@z 14g2000cwz.goog legroups.com...

Can anyone see whats wrong with this code:

The connections are remaining live in the database: and causing
"Timeout expired. The timeout period elapsed prior to obtaining a
connection from the pool" errors.

Try
'open the connection
myConnection.Op en()
'run the query
myCommand.Execu teNonQuery()
Catch ex As SqlException

Finally
'close connection
myConnection.Cl ose()

End Try

'Check to see if the service is restricted
If
myCommand.Param eters("@AccessR estrictionsSupp orted").Value.E quals(1)
Then
Return True 'service is restricted
'myConnection.C lose()
Else
Return False 'service not restricted
'myConnection.C lose()
End If

myConnection.Cl ose()

Any help/suggestions very much appreciated

Thanks!!

[Caro]

Timeouts when users logon to system.

Checked in enterprise manager - process info and there are lots of
active connections to the stored procedure that this piece of code
executes.

Thanks for your help

Much appreciated

"Gabriel Lozano-Morán" <ga************ @no-spam.com> wrote in message news:<eN******* *******@TK2MSFT NGP10.phx.gbl>. ..

close the connection immediatly after the ExecuteNonQuery () method call. You
don't need the myConnection.Cl ose() at the bottom since the finally block
will always be executed. When you close a connection it returns to the
connection pool where it will be destroyed after an idle period of 4 to 7.5
minutes.

Where do you exactly get the time-outs?

Gabriel Lozano-Morán

<ca***@orange.n et> wrote in message
news:11******** *************@z 14g2000cwz.goog legroups.com...

Can anyone see whats wrong with this code:

The connections are remaining live in the database: and causing
"Timeout expired. The timeout period elapsed prior to obtaining a
connection from the pool" errors.

Try
'open the connection
myConnection.Op en()
'run the query
myCommand.Execu teNonQuery()
Catch ex As SqlException

Finally
'close connection
myConnection.Cl ose()

End Try

'Check to see if the service is restricted
If
myCommand.Param eters("@AccessR estrictionsSupp orted").Value.E quals(1)
Then
Return True 'service is restricted
'myConnection.C lose()
Else
Return False 'service not restricted
'myConnection.C lose()
End If

myConnection.Cl ose()

Any help/suggestions very much appreciated

Thanks!!