I don't understand. When I look at both getConnection methods
in XAPoolDataSource, in the version on my disk and the latest version in
CVS Web (1.4), *there is no loop*!!! It just does
return ((XAConnection)pool.getObject()).getConnection();
Furthermore, the underlying pool itself *does* use wait and
notify. What on Earth are you talking about?
Aaron
On Sat, 7 Oct 2000, Daniel Schulze wrote:
> 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
>
