As you say i'd like to patch my 2.1.7 instead of going with a snapshot so if you could send me that mail over i can make the change.
Thanks again guys,
Paul
On 5/18/05, Ralph Goers <[EMAIL PROTECTED]> wrote:
Leszek,
I suspect Paul will want to patch 2.1.7 since that is what he has been
testing with (I doubt he wants to go into production with a snapshot).
Is there a possibility you can forward the svn email to him so he can
patch it himself?
Paul - If I misread you please speak up.
Ralph
Leszek Gawron wrote:
> Paul Crabtree wrote:
>
>> Hi all,
>>
>> This is kind of a repost but with more importance. We're due to go
>> live soon with the Cocoon project im working on but ever since an
>> upgrade to Cocoon 2.1.7 we've been experiencing
>> ConcurrentModificationException warnings from
>> ContinuationsManagerImpl.invalidateContinuations as Cocoon tries to
>> clear up old continuations (im assuming).
>>
>> I'm worried that perhaps these arent being cleaned up at all which
>> could be the start of a memory leak. We werent getting them on 2.1.6
>> and upgraded to 2.1.7 to gain the functionality of continuations
>> being bound to sessions that this upgrade offered.
>>
>> We're running Cocoon 2.1.7 on JBoss 3.2.5 on Java 1.4.2
>
> Vadim don't read this:) :This has already been fixed in trunk. Forgot
> to sync.
>
