tag:blogger.com,1999:blog-5874979429188093780.post6190789566310609400..comments2024-03-18T06:46:54.352+01:00Comments on Andrej Baranovskij Blog: How to Minimize Number of ADF BC Application Module ActivationsAndrej Baranovskijhttp://www.blogger.com/profile/04468230464412457426noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5874979429188093780.post-87938508400209556462014-11-06T20:27:57.869+01:002014-11-06T20:27:57.869+01:00As always, it is hard to advice production system ...As always, it is hard to advice production system settings. I can't recommend changing any tuning parameters, without checking the behaviour of your application.<br /><br />Especially for production, what will be if it will break after my suggestions? :-)<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-36706958602554721252014-11-06T10:22:04.834+01:002014-11-06T10:22:04.834+01:00Hi Andrejus,
Thanks for the useful information yo...Hi Andrejus,<br /><br />Thanks for the useful information you share regarding ADF. It clears our concepts more and more.<br />Currently we are using ADF 11.1.1.6.0 Webcenter portal application, and we are facing a lot of issues due to AM connection pooling, frequently NPE in production.<br /> <br />We have two AM across our application. <br /><br />Current settings of our AM is<br />Idle Instance Timeout = 600s<br />Pool Polling Interval = 600s<br />Initial Pool Size = 0<br />Max. Pool Size 4096<br />Referenced Pool Size = 10<br />Min. available size = 5<br />Max. Available Size = 25<br />Session Timeout in web.xml = 15 min<br />Timetolive=3600000<br />jbo.txn.disconnect_level = 1<br />jbo.doconnectionpooling = false<br />jbo.dofailover=false<br /><br />As per your post, our issue could be because of following reasons:<br /><br />The Session timeout > AM Idle Instance timeout<br />Time to live = 3600000<br />jbo.doconnectionpooling = false<br /><br />These issues are observed in Production env. only. We do not have any Preprod env. Hence to simulate load conditions is quite difficult.<br />Is it recommended to make below changes directly in production or should it be attempted one by one<br /><br />The Session timeout =15 min<br />AM Idle Instance timeout = 10 min<br />Time to live = -1<br />jbo.doconnectionpooling = true<br />jbo.dofailover=true<br /><br />Please suggest the best possible way to minimize these errors and not to create new errors.<br /><br />Regards,<br />Neha<br /><br />Nehanoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-75803676421012788292014-10-18T10:55:38.853+02:002014-10-18T10:55:38.853+02:00Hi,
On contrary, I recommend to set doconnectionp...Hi,<br /><br />On contrary, I recommend to set doconnectionpooling=true, check here: http://andrejusb.blogspot.com/2011/11/stress-testing-oracle-adf-bc_16.html<br /><br />Idle Instance Timeout must be greater than Web session timeout.<br /><br />If you want to support high availability, you should set doFailover=true.<br /><br />In general, tuning depends and differs for every ADF application.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-42944362972165696132014-10-17T06:05:59.505+02:002014-10-17T06:05:59.505+02:00Hi Andrejus,
I have read various blogs of yours r...Hi Andrejus,<br /><br />I have read various blogs of yours related to AM Fine tuning. Currently for our ADF 11.1.1.6.0 Version application we have lot of AM. We implemented Nested AM Concept as well. I have tuned AM Pooling parameters as below. Please suggust me whether i am ok or i need to do some thing better.<br /><br />AM Time to Live= sessiontimeout in web.xml<br />Idle instance timeout=5 min<br />Pool Pooling Interval=5 min.<br /><br />I have read some of your blog not to do doconnectionpooling = true due to activation/passivation cost. So i left that to default value. Is that ok.<br /><br />Also we have cluster environment, should i enable doFailover=true, but it says it also consumes more activations/passivations. should i enable it. Please give u r best answers.Srinivas Achantanoreply@blogger.com