FAQ

http://wiki.jboss.org/wiki/Wiki.jsp?page=WhatDoesTheMessageDoYourOwnHousekeepingMean

"teknokrat" wrote:
Ok, thanks. Is there a way to switch this off on a per connection factory level? I would like to get the benefits of the checking for database connections but not on my own session based connections.

// CMT Required Transaction
public void doSomething()
{
 ConnectionFactory cf = ...
 Connection c1 = cf.getConnection(); // Handle
 Connection real1 = c1.getRealConnection(); // Real

 Connection c2 = cf.getConnection(); // Handle
 Connection real2 = c2.getRealConnection(); // Real

 assert c1 != c2; // Handles are not the same instance
 assert real1 == real2; // But you always use the same real/underlying connection in the same transaction
}

"teknokrat" wrote:

Also, just out of curiosity, what is the heuristic that jboss uses to decide that a connection has been checked out of the pool long enough and needs closing?

"teknokrat" wrote:

If there are better ways to do this I am all ears.

The point I'm making is that you wouldn't do it that way (demarcate logon/logoff).
A user can logon and not do anything. You are wasting resources.

Instead you would allocate a connection for a unit of work (e.g. upload/download some files).
For each unit of work, you would "reauthenticate" based on the CRI or Subject.

That way you get maximum sharing of connections and you don't have
unused connections lying around when they are not being used.
The number of open connections is directly related to the number of active units of work,
not the number of SFSBs a lot of which could be idle.

This would be most efficient if the backend supports something like session suspension
as some telnet servers do.
Related to that is (if you are writing the back end yourself), you would be better using the
XAResource interface and storing the session against the XID on the backend server.
That way you can use "interleaving" where you start the session on one connection
suspend it (close() - returning the connection to the pool for somebody else to use)
and resume it on a different physical connection (or the same connection)
when you need it again.

e.g. psuedo code

ConnectionFactory cf = ...
Connection c = cf.getConnection(); // Allocate connection from pool - start the session - XAResource.start(xid, TMNOFLAGS);
Object data;
try
{
 data = c.download();
}
finally
{
 // Return the connection to the pool - suspend the session - XAResource.suspend(xid);
 c.close();
}

// Do some long running process, we don't need to have the connection for this
// so let somebody else use it!
Object result = calc(data);

Connection c = cf.getConnection(); // Reget a connection - resume the session - XAResource.start(xid, TM_RESUME);
try
{
 c.upload(result);
}
finally
{
 c.close();
}