Hi All ,
I have a piece of code for handling a documentum transaction . I use the transaction manager.beginTransaction to mark the boundary of the transaction and use Transaction Manager.commitTransaction after all the dfc calls are complete.
I print the number of active sessions before the commitTransaction method is called and exactly after the commit transaction is called using the result of "execute count_sessions" . But it seems that the commitTransaction is increasing the "Hot list" by 1 . And after the program exits the count still remains unchanged. I have wait 5 mins before the session is marked as inactive.
Any Idea how to avoid the extra session created by the commitTransaction method.
I am using DFC6.7 - JDK 5 on WAS
Code
-----------
IDfSessionManager sessMgr = getSessionManager(); // Custom method to get the Session Manager
.....
....
sessMgr.beginTransaction();
//DFC Calls
.......
.........
printSessionCount() // Output is 6
sessMgr.commitTransaction()
printSessionCount()//Output is 7
......
.....
......
Thanks