No, this is outside the realm of JBossJCA as stated here:
DataSource with internal pool
This is a non XA datasource that does its own pooling.
If you do this, you are outside JCA. The internal pool of the DataSource will not understand the transactions or security configuration. Nor will any other component that expects the connection to be controlled by JCA which does the JTA (transaction manager) integration.
These DataSources are intended for use outside a J2EE environment.
Consult your Oracle documentation and keep in mind that you are not using JBossJCA in this configuration.
Thank you for replying.
So am I stuck? how can I reset the connection pool in runtime? I would like to identify a situation where no more connections are available and reset the connection pool? will that work?
Can you provide the link to the JIRA task associated with the 'leak' in 3.2.5?