Disconnect Application Module Upon Release app module configuration.

Question

Hi,
I read in one article that using that "*Disconnect Application Module Upon Release*" in App module configuration is strongly not recommended (http://andrejusb.blogspot.com/2010/02/optimizing-oracle-adf-application-pool.html).
Can anyone pls let me know if there are any other problems apart from this (https://forums.oracle.com/forums/thread.jspa?messageID=9873898#9873898) LOV issue.

Answer 1

Hi Frank,
Thank you very much for your support.... very much needed.......
I will give a outline of my app and please do tell me where you need indepth details so we can narrow down to the flaw.
* JAVA : *1.6*
* JEVELOPER VERSION: *11*
* WebLogic : *11*
* Oracle DB : *11g*
----------------------------------------- ORACLE DATABASE DETAILS*
* VERSION : *11g*
* MAX CURSORS LIMIT : *300*
----------------------------------------- WEBLOGIC DETAILS*
* DATA SOURCE : XXXDS (Not jdbc url)
* JNDI : jdbc/XXXDS
* Connection pool details:
- initial size : *1*
- Max Capacity : *50000*
- Inactive connection time out : *0*
* Every other settings are defaults
----------------------------------------- AM's details*
* My model contains : *19* App modules ( All root )
* app module configs: (Giving only those were changed, else are defaults)
--- Connection type : Data Source - datasource name : jdbc/XXXDS (One given in weblogic)
--- jbo.ampool.maxinactiveage : *60000*
--- jbo.ampool.monitorsleepinterval     : *30000*
--- jbo.ampool.timetolive :*120000*
--- jbo.locking.mode : optimistic
----------------------------------------- Overridden Methods*
This method is called each and every time an app module since all appl modue extends this
@Override
protected void *prepareSession(Session session) {*
String username = ADFContext.getCurrent().getSecurityContext().getUserName().toUpperCase();
log.debug("Preparing session for user " + username);
Statement st = getDBTransaction().createPreparedStatement("rollback", 0);
try {
if (st.getConnection() instanceof PoolConnection) {
PoolConnection poolConnection = (PoolConnection) st.getConnection();
OracleConnection connection = (OracleConnection) poolConnection.checkConnection();
if (connection.isProxySession() && username.equals(connection.getProperties().get(PROXY_USER_PROPERTY))) {
// no proxying required, we already have a connection that is proxied for this user
super.prepareSession(session);
return;
clearStatementCache(poolConnection);
if (connection.isProxySession()) {
log.debug("Connection already proxied. Tearing down previous connection.");
connection.close(OracleConnection.PROXY_SESSION);
log.debug("Creating proxy connection for user " + username);
Properties properties = new Properties();
properties.put(PROXY_USER_PROPERTY, username);
connection.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, properties);
clearStatementCache(poolConnection);
validateUser(username);
} else {
throw new JboException("Connection was not a PoolConnection, your AppModule appears to be using JDBC URL configuration instead of a managed data source.\n Try changing the Local and Shared 'Configurations' for this application module: " + this.getDefFullName());
} catch (SQLException e) {
log.error("Unable to prepare session correctly, proxying failed.", e);
} finally {
try {
st.close();
} catch (SQLException e) {
log.warn("Unable to close statement", e);
super.prepareSession(session);
@Override
protected void beforeDisconnect() *{*
Statement st = getDBTransaction().createPreparedStatement("rollback", 0);
try {
PoolConnection poolConnection = (PoolConnection) st.getConnection();
clearStatementCache(poolConnection);
} catch (SQLException e) {
log.warn("Unable to tear down session correctly, clearing statement caches failed.", e);
} finally {
try {
st.close();
} catch (SQLException e) {
log.warn("Unable to close statement", e);
super.beforeDisconnect();
----------------------------------------- Few points about our design
* A single page can load more than one app modules.
* All LOV comes under a single app module.
* We use multiple LOV in the same page.
thank you for ur help......