You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jonathan Spaeth <Jo...@networktelephone.net> on 2003/06/05 23:38:49 UTC

RE: cvs commit: cocoon-2.1/lib/core rhino1.5r4-continuations-2003 0605.jar rhino1.5r4-continuations-20030323.jar

I am not sure if I have experience the exact bug you are referring to, but
the abstract description fits the behavior I have experience using the
cocoon-2.1-m2 release.  I esentially sent 7 or 8 requests to my webapp
simultaneously and 2 of them failed.

Im glad to see that this bug has already potentially been identified, but I
think you are potentially quite correct in your analysis.

If this turns out not to be the case, I can provide more detailed logs
regarding the continuations problems I have experienced with simultaneous
users.

Jon

-----Original Message-----
From: Steven Noels [mailto:stevenn@outerthought.org]
Sent: Thursday, June 05, 2003 4:21 PM
To: cocoon-dev@xml.apache.org
Subject: Re: cvs commit: cocoon-2.1/lib/core
rhino1.5r4-continuations-20030605.jar
rhino1.5r4-continuations-20030323.jar


On 5/06/2003 17:54 coliver@apache.org wrote:

> coliver     2003/06/05 08:54:40
> 
> Modified:    lib      jars.xml Added:       lib/core
> rhino1.5r4-continuations-20030605.jar Removed:     lib/core
> rhino1.5r4-continuations-20030323.jar Log: fixed serious bug in
> dynamic scope handling by the continuation enabled rhino interpreter
> that would cause intermittent failures when multiple users execute
> flowscripts from the same sitemap

I might be wrong, but I cannot see any commit in the cocoondev.org
rhino1_5R4pre module that reflects the fix of the bug your are referring
to. Looking at
http://lists.cocoondev.org/cgi-bin/ezmlm-cgi.py?6:dds:0:200303, I don't
see any commit mail messages neither, so I'm pretty sure the fix of that
bug lives on your harddisk only (or the mailing list software glitched
somewhere, and I should dive in and fix).

I really do hope something is wrong with my analysis, but if I'm right,
that means a vital part of the flow system, central to Cocoon-post-2.0,
is not under public source control. This worries me a lot.

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org