> > That's fine for now. Actually, the usage the store makes of the pool is not > > correct at the moment, so a partial rewrite will be indeed needed. > > Ok. I'll leave it as-is, then. If you have time to give me some hints as > to how the J2EE stores _should_ be using the connection pool, then > that'd be appreciated. I don't mind doing the work of actually rewriting > it, but I'm not sure (I haven't done much database stuff) where it is > appropriate to get a new connection, etc.
I think you need to associate 1 connection <-> 1 global transaction ID, and put back the connection in the pool at the end. That's also what Dirk suggested, if I remember well. IMO, you also can also fully rely on the DataSource TX isolation (or at least allow it as an option), and always accept enlistment in a transaction (the DB will then handle the rest, which could be finer grained, so it should end up being faster). Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
