Passivation table ps_txn not being cleaned up

Question

Adf 11gR1PS1
Hello
I have a samll application using one unbounded task flow and one bounded task flow.
Each task flow uses a different application module.
The unbound task flow calls the bounded task flow in a modeless inline-popup via a button.
When running the application and clicking on the button the bounded task flow is called and a new row is inserted
into the ps_txn table.
However when the inline-popup is closed via the "x" on the popup window the row is not removed from the ps_txn table.
If the button is clicked again a new row is added to the theps_txn table.
Is this the normal behaviour, looking at 40.5.3 in the Dev Guide it would seem that the record should be deleted or reused.
I understand that there are scripts for cleaning up the table but shouldn't it be automatic ?
What am I missing ?
Regards
Paul

Answer 1

Hi Paul,
Do you use the failover (jbo.dofailover) ?
If not, I would expect records to be deleted from PS_TXN at activation.
I tested with the ADF BC Component Browser, selecting menus Save/Restore Transaction State, with jbo.debugoutput=console:
[277] (0) OraclePersistManager.deleteAll(2126) **deleteAll** collid=17461
[278] (0) OraclePersistManager.deleteAll(2140)    stmt: delete "PS_TXN" where collid=:1
[279] (0) OraclePersistManager.commit(217) **commit** #pending ops=1But I also already noticed orphaned records in the table.
Do you use jbo.internal_connection to use the same connection whatever the AM instance that's passivated/activated or do you have an instance of the PS_TXN table in all AM's connections ?
Regards,
Didier.