| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.misc -> Re: ASP script hangs on ADO Open
We have the same problem. Initially we were three asp apps in their own address space and at least one of the three would start failing 100% soon after restart.
We're now running them in IIS space, and the problem is much more intermittent.
Incidentally, before we made the switch, there was exactly one connection
for every asp app that hadn't timed out, and a corresponding mtx.exe at the
NT end. After we made the switch, there is only one connection showing at
the Oracle end. What I'm wondering is what this says about connection
pooling:
- We've got it turned off?
- It only uses multiple connections when there are seperate asp apps running
in their own space?
Hmm.
>
>Hello!
>I had exactly the same problem...
>I can say that on IIS3.0 all works fine! (I upgraded server, because I need
>more complex actions with files via ASP)
>I tried to open and close new Connection on every page (dont use single
>Connection per ASP Session) - result the same.
>Finally, I rejected to use ADO and ODBC, and install the Oracle Objects for
>OLE. I think Oracle corp knows better how to work with Oracle Database :)
>
>Geoff Dawson wrote in message <6foo58$nul$1_at_hagen.usenet.co.uk>...
>>I am using ASP and ADO to connect to an Oracle database. Versions are IIS
>>4.0 and MDAC 1.5c with both the Microsoft ODBC driver 2.73.728303 and the
>>Oracle ODBC driver 2.05.031. It works with a single client connecting even
>>with a fast hit rate (using an automated client gives over 10 accesses per
>>sec). But with more then one client it hangs. Poking around with a test
>>script shows that any ASP script attempting to Open an ADODB Connection
then
>>hangs even if it is to a different (non-Oracle) database.
>>
>>The Oracle database is fine and I can still connect to it manually on the
>>server using ODBC.
>>
>>At that point I cannot cleanly close down the Web Service. Using 'net stop
>>iisadmin' reports that the service could not be stopped and reports System
>>error 1051.The only solution seems to be a server re-boot.
>>
>>Unfortunately I had not tested concurrent access before upgrading to IIS
>>4.0.
>>
>>Any suggestions ???
>>
>>Geoff Dawson
>>
>>
>>
>>
>
>
Received on Wed Apr 08 1998 - 00:00:00 CDT
 |
 |