I was able to get a patch that seems to work. There were only two transactions in SVN required for a back-port:
http://svn.apache.org/viewvc?view=rev&revision=56921 http://svn.apache.org/viewvc?view=rev&revision=57424 I hope nobody else has to do this... but hopefully this information will be useful if they ever have to repeat this patching fun! -Stephen Stephen Connolly-2 wrote: > > Thanks for that Jörg, > > Hopefully I can use this information to derive a patch for 2.1.5.1 > > -Stephen > > > Joerg Heinicke wrote: >> >> Stephen Connolly-2 <stephen.alan.connolly <at> gmail.com> writes: >> >>> We have an application that is using Cocoon 2.1.5.1 (I know that's a wee >>> bit >>> old) >> >>> With the application IDLE, no clients have even attempted to connect. >>> >>> We see on Windows a handle leak at a rate of approx 64 handles (32 Event >>> and >>> 32 Semaphore) every 5-6 seconds. >> >> Searching the archives I found COCOON-1305 [1]. Somewhere in the middle >> (around) >> discussion points to TPCThreadManager which was used by >> ContinuationsManager. >> Unfortunately, there is no fix/patch linked explicitly but on 12/Nov/04 >> it is >> confirmed that the issue is fixed: "Migration from Excalibur Event to >> RunnableManager fixes this bug IMO." So I guess you can have look at the >> changes >> from around that time. >> >> Hope this helps, >> Joerg >> >> [1] http://issues.apache.org/jira/browse/COCOON-1305 >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- View this message in context: http://www.nabble.com/Cocoon-2.1.5.1-and-Windows-Handle-Leak-tp19430635p19458053.html Sent from the Cocoon - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
