Note that there are some explanatory texts on larger screens.

plurals
  1. POOracle connections exhausted by IIS
    primarykey
    data
    text
    <p>Our Oracle (9i) DBA called me to report that my IIS (v6) web server has exhausted the available connections. </p> <p>I created a test page (Classic ASP) that basically creates ADODB.Connection and ADODB.Recordset objects, connects to a database, opens a basic recordset, loops through it, closes the recordset and connection and sets the objects to nothing. This is what most of the applications on the web server do.</p> <p>While speaking with the DBA I opened the test web page. The DBA was able to see that I connected and noted the <em>ID</em> (I assume this <em>ID</em> helps him track the connection). The page finished loading, therefor, the Close method of both objects <strong>have</strong> occurred.</p> <p>The DBA said that the connection was still showing, even after I closed the browser.</p> <p>Eventually the connection went away, I assume because the Application Pool recycled.</p> <p>So my question is: Is this normal? Should the connection not go away after the Close method is called.. or at least the session is closed?</p> <p>I'm not sure if this is helpful or even related, but we've seen these errors periodically in the event viewer on the our web servers:</p> <pre><code>Event Type: Information Event Source: Application Error Event Category: (100) Event ID: 1004 Date: 7/21/2010 Time: 7:34:20 AM User: N/A Computer: VMADE02 Description: Reporting queued error: faulting application w3wp.exe, version 6.0.3790.3959, faulting module orantcp9.dll, version 9.2.0.6, fault address 0x00005741. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload