In the normal world of JDBC, dealing with a transaction is trivial -
get a connection, set the auto commit to false, do your stuff, call
commit() if you're happy, call rollback() if you're sad, and close.
Connection Pools are supposed to avoid the overhead of repeated
connections to the database, and I was mistakenly under the assumption
that little else changed. JBoss allows you to get a context, and from
the context a connection pool, to which you use it, and upon closing,
the connection is returned to the pool. However, there are several
oddities I think I need explained by someone who's walked over this
ground before.
I'm aware that with JBoss's managed connection pool, one cannot call
setAutoCommit() -- fine, it default to false, which is what I want
anyhow.
But I can't seem to call commit() or rollback() either. Is there some
other call I'm supposed to be using?
And the really weird part... even after I perform a close(), the
transaction doesn't seem to commit immediately.
Unfortunately, Googling for JBoss managed connection pools doesn't
get much useful information.
Can got any clues or can point me at an online reference about JBoss's
behavior for managed connections?
thx.
-wls@[EMAIL PROTECTED]
|
