> I actually haven't measure performance. Surely there is overhead managing > individual connection close attempts. Spring manual recommends to avoid > dataSourceProxy. All needed to be done was calling release instead of close > on connection, now transactions work without proxy. I use poolable data > source so I thought they will be just returned to pool on close and obtained > back on next getConnection() call within transaction.
I didn't know Spring had a different implementation on the Connection.close() method... I guess these things are often implementation-dependent...
