The transaction does not die after the kill and I have to restart Oracle

Question

Hi,
I have this very hard issue with my production environment.
A transaction started from java hangs after the user has closed the browser before the transaction was completed. The transaction remains in wait for "latch free" in v $ transaction.
When the WebSphre is stopped the transaction is not closed. Neither the kill on Oracle or on Unix conclude the transaction. The restart of the DB is required.
The rollback segment pointed to by the transaction is always the same. Although the procedure call by java is always the same.
The database does not have performance problems and only one transaction per day waits for "latch free" and do not closed.
The problem could be the rollback segment? Why Oracle is unable to resolve the transaction even if the client is dead and the WebSphere off?
Regards,
BingoBongo

Answer 1

The average duration of the transaction is 10/15 seconds.
When it lasts longer the client is closed and the transaction remains locked. But not always only in a particular case.
From this moment the transaction is waiting for "latch free" and the value of the field USED_UBLK/USED_UREC does not increase and not decrease.
The wait event is always the "latch free".
The kill (Unix, Oralce) has no effect on the transaction.
The rollback segment is always the same.
The procedure call is always acts the same.
The value of "SECONDS_IN_WAIT-WAIT_TIME/100" increases up to a certain point and then start over again.
This is a snapshot of a transaction that requires restart of the DB:
STATUS
SECONDS_IN_WAIT-WAIT_TIME/100
CR_CHANGE
XIDUSN
SECONDS_IN_WAIT
WAIT_TIME
STATE
EVENT
USED_UBLK
USED_UREC
OSUSER
CLIENT_INFO
ROW_WAIT_BLOCK#
ROW_WAIT_OBJ#
PROGRAM
MODULE
ACTIVE
399,99
178
10
400
1
WAITED KNOWN TIME
latch free
11
738
was5a
0
56204
JDBC Thin Client
JDBC Thin Client