Hi,
First off, I'm fairly new to Ant and jUnit so I've been unable to run the
testcase org.apache.avalon.excalibur.pool.test.PoolProfile which I believe
tests SingleThreadedPool.
"build.bat" test doesn't seem to run the test either.
I've encountered a problem with the SingleThreadedPool in that it
alternatley returns valid and null pooled objects until you've got the
"initial" constructor argument + 1 and then it starts returning
(Poolable)m_factory.newInstance(). Does that make sense? This effect is only
seen if you call a method on the object returned from the pool. The
PoolProfile class simply "get"s from the pool and then "put"s into the pool.
If methods were added to the static classes inside PoolProfile and
PoolProfile were to call these methods between gets and puts I think this
could be demonstrated. I've attached a patch for SingleThreadedPool that I
believe fixes this.
Corey
SingleThreadedPool.patch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
