Re: Tx - row lock contention after implementing transaction management in application server
Date: Sun, 31 May 2009 13:41:43 +0700
I have the same experience with something similar to your environments...
it was java + bea + hibernate + 10.2.0.3 database. the problem is similar - tx row lock contention.
all the PK-FK has been indexed, and nothing issue in the database side, so after long investigation the problem is due to small number entity bean against transaction request from the front end.
-- thanks and regards ujang | oracle dba | mysql dba Jakarta - Indonesia On Wed, May 27, 2009 at 1:41 AM, dd yakkali <dd.yakkali_at_gmail.com> wrote:Received on Sun May 31 2009 - 01:41:43 CDT
> Hello everyone,
> After our application folks implemented transaction management in the app, I
> am seeing a bunch of seesions waiting with "Tx - row lock contention" on an
> insert statement. we found that the parent table insert is not commited and
> hence the child record insert is hanging as both these statements are using
> different oracle sessions for some reason. This continues for eternity,
> until the app server is killled and restarted.
> Sun Java Enterprise Server, hibernate, oracle 10.2.0.4 RAC.
> Now here is the question: Our java app server folks are asking me to give
> them bind variable values of the statement that is hanging. We have a
> connection pool which is 132 connections size. Is there any way to get the
> bind variable values after the fact, i.e while it is waiting for the parent
> to commit?