Re: OWS problem

Yes its the good 'ol server too busy OWS problem.

We have exactly the same problem with OWS 2.1 on HP-UX, 'stop', 'back', 'forward' browser buttons somehow sever the connection and continue to use up db sessions, both pl/sql, java jobs become zombie processes, still executing until completion but not freeing up session, only remedy by forcing web listener to stop/start which is useless when environment goes live.

A few people profess to having "Oracle Webserver" powered sites, and when I test back,forward,stop they don't seem to crash -am I missing something? or are their session numbers ridiculously large ie. 500, and they had to write some daemon to kill off sessions -I hope this isn't the case :)

Incidently, I tried to manually kill off pl/sql jobs but this did not restore sessions lost, I still had to restart listener.

I'm trying to track down a timeout command in Webserver or SQLNET but so far have found nothing (SQLNET timeout doesn't appear to work), does any one out there have a solution?

Any help gratefully received.

• Mark.

Dan Saunders wrote:
>
> We are having a problem with OWS 2.1.
>
> The problem is this:
> If a user requests a page that is generated by pl/sql, and then
> cancels it before it has been returned, the database connections will
> no longer function. This can be easily reproduced. We must limit our
> OWA connections to 16 due to the load generated on our database
> machine. After 16 people have cancelled requests, the server is
> useless.
>
> We are using NT 3.51, and OWS 2.1 or 2.0 (They both have this
> problem).
>
> Our database machine is a sequent running oracle 7.1.6.
>
> Please help!
>
> Thanks!
>
> Dan Saunders
> University of Idaho
Received on Mon Apr 28 1997 - 00:00:00 CDT