Hi,

I have a site that is very data-centric and I'm trying

to gracefully handle situations when our Oracle server

might go down. As it is now, if the Oracle DB stop, or

the Oracle Listener stops, or if the server that

Oracle runs on shuts down then my inetinfo.exe process

uses 100% of CPU and memory within about a minute. IIS

never seems to be able to recover once Oracle is back

online and I have to reboot. 



I have a short include file that simply makes an ADO

connection before any other code runs or any HTTP

Header info is sent to the client. If there is any

errors, redirect to a static HTML page. I'm testing

the ADO Connection for errors like this..



If objConn.Errors.Count <> 0 Or Err.Number <> 0 Then

   Response.Redirect("static.html")



This is working correctly, however it seems that it

doesn't immediately detect a problem with this

connection. For example, If I stop the Oracle listener

and then immediately request a page it will continue

as if there were no problems for about 60 seconds

before finally redirecting. Then it will continue to

work for as long as I leave the Listener down. Bring

it back up and it takes another 60 seconds before it

stops detecting an error. I don't think this is a

browser caching problem because I've dropped the

listener and then tried from a couple computer that

have never request from this particular web server

before. I should also mention that when I drop the

listener and then immediately try to connection to

that DB from other Applications (that are dependant on

it) the apps detect a problem right away.



Any ideas why it takes so long for my error handler to

report a problem?



thank you,

Craig Shields

Not being Oracle specific, but more of a general thought. Most of these

timeouts work on wait states (e.g., if you haven't responded in x seconds,

I'll consider you gone). You may be able change your connection properties

to shorten that.



kt



On Mon, 19 Feb 2001, Craig Shields wrote:



> Hi,

> I have a site that is very data-centric and I'm trying

> to gracefully handle situations when our Oracle server

> might go down. As it is now, if the Oracle DB stop, or

> the Oracle Listener stops, or if the server that

> Oracle runs on shuts down then my inetinfo.exe process

> uses 100% of CPU and memory within about a minute. IIS

> never seems to be able to recover once Oracle is back

> online and I have to reboot. 

> 

> I have a short include file that simply makes an ADO

> connection before any other code runs or any HTTP

> Header info is sent to the client. If there is any

> errors, redirect to a static HTML page. I'm testing

> the ADO Connection for errors like this..

> 

> If objConn.Errors.Count <> 0 Or Err.Number <> 0 Then

>    Response.Redirect("static.html")

> 

> This is working correctly, however it seems that it

> doesn't immediately detect a problem with this

> connection. For example, If I stop the Oracle listener

> and then immediately request a page it will continue

> as if there were no problems for about 60 seconds

> before finally redirecting. Then it will continue to

> work for as long as I leave the Listener down. Bring

> it back up and it takes another 60 seconds before it

> stops detecting an error. I don't think this is a

> browser caching problem because I've dropped the

> listener and then tried from a couple computer that

> have never request from this particular web server

> before. I should also mention that when I drop the

> listener and then immediately try to connection to

> that DB from other Applications (that are dependant on

> it) the apps detect a problem right away.

> 

> Any ideas why it takes so long for my error handler to

> report a problem?

> 

> thank you,

> Craig Shields

> 

>