On Wed, 2003-09-03 at 11:05, Carsten Ziegeler wrote: > Bruno Dumon wrote: > > > > On Wed, 2003-09-03 at 10:23, Carsten Ziegeler wrote: > > <snip/> > > > I think we should do this switch asap. *If* we can solve the > > commandmanager > > > issue discussed in the other thread, I will make a 2.1.1 > > release this week. > > > > The issue can in fact be fixed immediately by changing the way we use > > the PooledExecutor class. In the TPCThreadManager class (in > > excalibur-event), change the line: > > > > m_threadPool.waitWhenBlocked(); > > > > to > > > > m_threadPool.discardWhenBlocked(); > > > > functionally, this shouldn't change anything (I think), and it will > > avoid the problem in PooledExecutor completely. If you have some time > > available to try this out, that would be great. > > > Yes, I just tried it - and it works. Great! > > So, how do we proceed?
I'd wait till tomorrow -- I should have a definitive answer from Doug Lea by then. > We can distribute our own patched version of event > or we can ask that this will be changed in excalibur. and then it can as well be patched in excalibur itself. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
