Closing pooled connections?? one at a time?

Question

I've got an interesting need;
I've writen a custom UserManager for form based authentication.
class ValidateLoginManager extends AbstractUserManager
Authentication is to a legacy DB (Oracle) where all users have
been added as
Oracle users. So I've created a separate JNDI data source in
data-sources.xml
for pooling connections that I'll only use for authentication
(just a gut decission).
The container calls:
boolean checkPasswd (username, passwd) {
boolean authenticated = false;
try {
dbConnection = this.datasource.getConnection(username,
passwd);
authenticated = true;
} finally {
if (dbConnection != null)
dbConnection.close();
return authenticated;
This works great, since Oracle authenticates the connection
against it's user DB.
But the conn.close() does not close the session on the DB and
soon all MTS tasks are used up in idle sessions.
Any thoughts on forcing the connection to drop open sessions?
thanks, curt

Answer 1

Hi Curt,
For my custom usermanager I use a datasource specified in my data-sources.xml like this:
<data-source
     class="com.evermind.sql.DriverManagerDataSource"
     name="xyz"
     location="jdbc/OracleSecurityDS"
     xa-location="jdbc/xa/OracleXADS"
     ejb-location="jdbc/OracleDS"
     connection-driver="oracle.jdbc.driver.OracleDriver"
     url="jdbc:oracle:thin:@127.0.0.0:1521:xyz"
     inactivity-timeout="30"
/>
When you lookup the datasource using JNDI, make sure you use the name bound to the location specified in the "location" attribute and not the "ejb-location" attribute (as you usually do in your Ejbs).
I hope this helps.
- nik.
I've got an interesting need;
I've writen a custom UserManager for form based authentication.
class ValidateLoginManager extends AbstractUserManager
Authentication is to a legacy DB (Oracle) where all users have
been added as
Oracle users. So I've created a separate JNDI data source in
data-sources.xml
for pooling connections that I'll only use for authentication
(just a gut decission).
The container calls:
boolean checkPasswd (username, passwd) {
boolean authenticated = false;
try {
dbConnection = this.datasource.getConnection(username,
passwd);
authenticated = true;
} finally {
if (dbConnection != null)
dbConnection.close();
return authenticated;
This works great, since Oracle authenticates the connection
against it's user DB.
But the conn.close() does not close the session on the DB and
soon all MTS tasks are used up in idle sessions.
Any thoughts on forcing the connection to drop open sessions?
thanks, curt