] Database locking and deadlock
Vic,
Yes, I do get a deadly embrace or deadlock, as the
row locks on the table multiply when they occur,
holding up connections in the connection pool,
eventually consuming all connections, and then all
hell breaks loose.
Were you referring to synchronizing
: Monday, March 08, 2004 6:36 PM
To: Struts Users Mailing List
Subject: Re: [OT] Database locking and deadlock
Vic,
Yes, I do get a deadly embrace or deadlock, as the
row locks on the table multiply when they occur,
holding up connections in the connection pool,
eventually consuming all
On 08/03/2004 21:31 Shyam A wrote:
[snip]
Is there a possibilty of a deadlock occuring in the
above code when there are mutliple users concurrently
accessing the system.i.e, multiple users update
multiple rows of the table at the same time
I can't see anything in your update that might cause
From a pure Oracle perspective I would program this more defensively
e.g Do a select for update nowait before you issue the update to grab
the lock in advance. That way you'll get an oracle error (ora -54) if
another user has the row and you can handle it appropriately
Duncan
Shyam A wrote:
Duncan,
Thanks for the suggestion. I was aware of that and did
consider the option. However, after consulting with my
DBA and doing some research, it seems the problem lies
with the number of concurrent transactions that can be
done on a table. This can be configured in the
INITRANS parameter for
Hi,
I know the subject of my mail is off-topic but I hope
somebody will be able to help me out with my problem.
I experienced a wierd problem today when a deadlock
occured in my database - Oracle 9i, and it locked up
all connections in the connection pool on my server -
OC4J (Oracle 9iAS). I
PROTECTED]
Subject: [OT] Database locking and deadlock
Hi,
I know the subject of my mail is off-topic but I hope
somebody will be able to help me out with my problem.
I experienced a wierd problem today when a deadlock
occured in my database - Oracle 9i, and it locked up
all connections
connection
each time which could possibly use up (exceed max
allowed) the connections in the pool.
Just a guess.
robert
-Original Message-
From: Shyam A [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 4:32 PM
To: [EMAIL PROTECTED]
Subject: [OT] Database locking
-
From: Shyam A [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 4:32 PM
To: [EMAIL PROTECTED]
Subject: [OT] Database locking and deadlock
Hi,
I know the subject of my mail is off-topic but I
hope
somebody will be able to help me out with my
problem.
I experienced a wierd problem today when
Message-
From: Shyam A [mailto:[EMAIL PROTECTED]
Sent: Monday, March 08, 2004 4:32 PM
To: [EMAIL PROTECTED]
Subject: [OT] Database locking and deadlock
Hi,
I know the subject of my mail is off-topic but I
hope
somebody will be able to help me out with my
problem.
I
Is there a way you can reproduce this w/ iSQL command line?
I assume Sybase, since you said row-level.
My guess is that it's not the sql, but your DAO logic somehow. It would
take you only a day or so to switch that one update to
http://www.reumann.net/do/struts/ibatisLesson1
.V
Shyam A wrote:
Vic,
Thanks again. I'm not in a position to switch to
IBatis as my application is currently in use. Right
now, I'm manually killing the user sessions which lock
up the table in the database. My database is Oracle
9i, and this problem seems to occur only with large
numbers of concurrent users. In
Do you have a deadly embrace?
Maybe just syncronise w/ semaphorse or the like.
.V
Shyam A wrote:
Vic,
Thanks again. I'm not in a position to switch to
IBatis as my application is currently in use. Right
now, I'm manually killing the user sessions which lock
up the table in the database. My
Vic,
Yes, I do get a deadly embrace or deadlock, as the
row locks on the table multiply when they occur,
holding up connections in the connection pool,
eventually consuming all connections, and then all
hell breaks loose.
Were you referring to synchronizing with semaphores?
I read somewhere
14 matches
Mail list logo