title: Connection Pooling with VB.NET and orphaned connections
body: <p>I am a DBA, not a developer, and could use some insight. The development staff is using VB.NET to create web based applications with connections to a DB2 database. Please assume that the connection string in the web.config file is coded correctly.</p>
  
  <p>I can see the number of orphaned connections from the web servers grow over time. By orphaned I mean that there is no activity associated with the connection for hours, yet I can see other connections being created and destroyed every couple of seconds.</p>
  
  <p>I suspect that the connections are not being properly closed, but there are two different groups looking at the problem and so far haven't turned up anything. By the end of the day I can have hundreds of these connections - all of which are cleared when the application pool is reset every night. (This means it is NOT a database problem)</p>
  
  <p>Is there a coding technique to ensure a connection is closed using vb.net on IIS v7+?
  Am I seeing the symptom of another problem on IIS?</p>