Use of Remote JDBC SQL Database External Resource

Question

Does anybody here uses a Remote JDBC External Resource to connect to a database? If so, can you tell me if had any impediment with this approach?
I'm asking this because our company has a lot of tools to monitor a lot of weblogic assets (such as jdbc connection pools and datasources) and We'd like to monitor all BPM-to-database connections usage and pool health. Other feature that we'd like to give to BPM application is the weblogic's capability to use an Multi-DataSource (one logical DS that represents more than one phisical DS).
Thanks and Best Regards,
Luiz Rocha

Answer 1

Hi,
We are facing connection leak in our application .We have defined External resouce as Remote JDBC which is defined in weblogic config.Xml. If any body could explain is there is anyway to handle closing connections manually as we do in J2ee conn.close() in ALBPM ??? . I found runtime configuration in oracle implementation type when defining external resource (i.e supported type:oracle database) an attribute
"*Connection idle time* (mins): The connection is closed after the defined time"
But i dont find any equivalent entry in my config.xml as we do our implementation of type Remote JDBC.....
Any advice on this and how connection closing happens in Normal scenarios within ALBPM will be very useful.
Our connection pool attributes reads like.....(Note *the values of few attributes deleted)
<JDBCConnectionPool AddOracleFlagToXAResource="true"
CountOfTestFailuresTillFlush="1"
DriverName=""
InitialCapacity="150" KeepXAConnTillTxComplete="true"
MaxCapacity="200" Name=""
PasswordEncrypted=""
Properties="user=" ShrinkingEnabled="false"
SupportsLocalTransaction="true" Targets=""
TestConnectionsOnCreate="false" TestConnectionsOnRelease="false"
TestConnectionsOnReserve="true"
TestTableName="SQL SELECT 1 FROM DUAL"
URL=""
XARetryDurationSeconds="300" XASetTransactionTimeout="true" XATransactionTimeout="420"/>
.Advice us can the below attribute can be added in Connection pool properties or anything else......
**{[(*Inactive Connection Timeout The number of inactive seconds on a reserved connection before WebLogic Server reclaims the connection and releases it back into the connection pool.***
***You can use the Inactive Connection Timeout feature to reclaim leaked connections - connections that were not explicitly closed by the application. Note that this feature is not intended to be used in place of properly closing connections.***
***When set to 0, the feature is disabled*.)}]**