Aaron,
meanwhile I had a look at the minerva code
(XAPoolDataSource.getConnection (*) lines 167-183).
The problem is exactly what I assumed it is...
A fragment like:
Object o = null;
while ((o = pool.getObject()) == null);
return ((XAConnection)o).getConnection ();
would fix the problem in both getConnection methods.
But instead of this ugly cpu killing loop, I think it would be better
to set the pool used by this DataSource object always to blocking. (So
that the cpu killer is only on one place ;-)
Tell me what you think of it and if you will fix it or if I should do
it!
/bye Daniel
