Re: table locking question

well what if you have a web application with say 50 userse. often times you wont run those in shared server mode.

is there any documentation on resolving deadlocks? not just avoiding them.

its not just a deadlock though. User A locks a row. User A gets disconnect. Row is still locked. Noone else can touch the lock until its released.

my undrestanding is that its only a 'deadlock' if User A and User B block each other?

<Kenneth Koenraadt> wrote in message
news:3e3c0aaa.4004057_at_news.inet.tele.dk...
> On Sat, 01 Feb 2003 17:51:24 GMT, "Ryan" <rgaffuri_at_cox.net> wrote:
>
> >I have seen this question posted in other places without adequate
answers. I
> >think this happened to me one time as well.
> >
> >If you are connected to the internet through the web and lock a row. You
> >lose your connection. Lock stays on. My assumption is you have to kill
the
> >session.
> >
> >What if you have 500 users and this happens. What is the best process for
> >automonitoring this?
> >
> >
>
> Hi Ryan,
>
> In public web-based application with 1000s of simultanous users,
> end-users rarely get their own dedicated server session. The server
> would simply run out of resorces, because of all the dedicated server
> processes that would be generated. The application would thus also be
> very vulnerable to DOS-attacks.
>
> Instead MTS (Multi-threaded server) or some kind of connection pooling
> (either provided by Oracle or other SW vendors) is used.
>
> When you have an in-house application with 500 users and you run in
> dedicated server mode, there are several ways to limit dead-lock. The
> best approach is usually to design the application to handle
> deadlocks. Oracle Server has the ability to and will detect deadlocks
> and resolve them, but ideally, deadlocks should be avoided, not
> resolved.
>
> - Kenneth
>
> - Kenneth
>
>
Received on Sat Feb 01 2003 - 13:48:10 CST