UI Shell template - jdbc connections

Question

We are using UI shell for our app so we could open mutliple tabs in the application, each tab opens a bounded Task flow with "Always Begin new Transaction" and "No Share Data Control". We limit total no of tabs that a user can be open to 10.
The problem is because of "Always Begin new Transaction" the data Control (Frame) is holding a DB connection for each tab, so potentailly each user can user or an AM instance can hold up to 10 DB connections.
My question is , IS there away to release DB connection of Data Control (Frame) when the TAB is not active and DB connection for the TAB this currently active, so we can limit the no of DB connections for the app?
Thanks
Ramesh

Answer 1

Hi Ramesh
Your conclusions here on why your app is taking is taking out 10 connections is nearly right, but it's the isolated data control scope that causes this, not the Always Begin New Transaction option. Please consult the paper "ADF Task Flow Transaction Fundamentals" and the 3 relating demos on the ADF Architecture Square to get a solid understanding of this:
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/adfarchitect-1639592.html
Those options alone don't control that the connections will be pinned to a particular user session. You'll be familiar that ADF BC Application Module pool parameter control how the AMs activate/passivate, connect to the database and so on. One option to pay attention to is the jbo.doconnectionpooling option (which is false by default).
This poorly named options would be better named "Disconnect Application Module Upon Release". What it does when false:
* AM will attempt to hang onto JDBC connection when finished working with request
* JDBC connection can keep open prepared statements over check in/out from pool
* If AM is given to new user, rollback called to clear state + AM prepareSession()
* Faster performance for users assuming they get served same AM
* But limits scalability, connections are pinned to AM
What it does when true:
* AM will drop JDBC connections on completion of request
* Increases scalability, connections can be reused
* Forces activation/passivation for every request
* AM prepareSession() called every new request
* User performance is slower as prepared statements aren’t cached
As such you might want to consider setting this to true.
Regards,
CM.