Transaction not abandoned

Question

Using Weblogic 6.1sp1 and oracle 8.1.7 with Stateful Session bean wrapping
          an entity bean.
          The stateful session bean has a save method that calls various methods in
          the entity bean to perform the save.
          The save method is marked as transaction requires NEW, the entity bean
          method are marked transaction required.
          I have configured the timeout to be 120 seconds and the abandon timeout to
          be 120 seconds.
          I enter a SQL command tool and lock the table I wish to update.
          I then attempt to call the save method on the session bean that will update
          the table.
          After 120 seconds, the method call does not return, it stays there continue
          to attempt the SQL operation.
          After 180 seconds I release the lock on the table.
          The method continues and then throws a RemoteException with a long internal
          exception.
          Should not the transaction be abandoned and return after the 120 seconds are
          up?
          Is there any way to catch this timeout and deal with it in my bean(s) so the
          ugly RemoteException does not get back to my client?
          Any help here is appreciated.
          Regards,
          Bruce
          

Answer 1

Use v$transaction view to check uncomiited transactions.
See here it's already discussed:
Re: How to query uncommited transactions
Locked objects can find with this select:
select
c.owner,
c.object_name,
c.object_type,
b.sid,
b.serial#,
b.status,
b.osuser,
b.machine
from
v$locked_object a ,
v$session b,
dba_objects c
where
b.sid = a.session_id
and
a.object_id = c.object_id;