tag:blogger.com,1999:blog-5874979429188093780.post57162451930676768..comments2024-03-18T06:46:54.352+01:00Comments on Andrej Baranovskij Blog: Oracle ADF BC 11g Tuning for Immediate Row Level LockingAndrej Baranovskijhttp://www.blogger.com/profile/04468230464412457426noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5874979429188093780.post-82134880259777657062010-12-03T02:38:20.575+01:002010-12-03T02:38:20.575+01:00Hi,
May be AM instance time to live should be inc...Hi,<br /><br />May be AM instance time to live should be increased, to be larger than heart beat period.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-79688867980039116572010-12-03T02:32:15.513+01:002010-12-03T02:32:15.513+01:00Hi Andrejus,
Thanks for the useful article, I als...Hi Andrejus,<br /><br />Thanks for the useful article, I also read Optimizing Oracle ADF Application Pool.<br />I have an issue with Application Module (AM) session, I have at least four AM, 'orders' is the most important.<br />In my adf application it is neccesary high availability for long periods of time, like three hours, few users.<br />It was developed a 'heart beat' implementation, in order to prevent that application session be destroyed, it works.<br />In web.xml, session timeout is 30 minutes, but 'heart beat' prevent a logout. <br /><br />The problem is:<br />Like a Viewer profile, like me, I am monitoring if everything is ok, I can have my application session forever opened and jump between JSPXs without problems (I go to lunch, when I come back the screen is the same, then I invoke a refresh button, and it works). <br /><br />but Operators use the principal AM a lot, and they have problems related with the AM, it seems that our AM, in some point, doesn't care about 'heart beat', and invokes logout, no matter if there is a proccess pending to be done, like an execution of an stored procedure. <br /><br />We don't have problems with datasource pool. AM pool size, AM time to live, have the defaults: maximum pool size and referenced pool size are set to 4096 and 10. jbo.ampool.timetolive:3600000. The problem is not a profile issue, if I'd use the AM it wouldn't work neither. <br /><br />Please advice me..<br />Thanks,<br />MyriamAnonymousnoreply@blogger.com