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