Re: Tx - row lock contention after implementing transaction management in application server
From: Martin Berger <martin.a.berger_at_gmail.com>
Date: Tue, 26 May 2009 20:57:56 +0200
Message-Id: <A784249A-343C-428C-AEFE-97AC1597FE5D_at_gmail.com>
Deen,
Date: Tue, 26 May 2009 20:57:56 +0200
Message-Id: <A784249A-343C-428C-AEFE-97AC1597FE5D_at_gmail.com>
Deen,
maybe you want to start with
http://laurentschneider.com/wordpress/2007/05/vsql-and-bind-variable.html
hh,
Martin
-- http://www.freelists.org/webpage/oracle-l Am 26.05.2009 um 20:41 schrieb dd yakkali:Received on Tue May 26 2009 - 13:57:56 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?
>
>
>
> Thanks
> Deen
-- http://www.freelists.org/webpage/oracle-l
- application/pkcs7-signature attachment: smime.p7s