cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Szymon Stasik <>
Subject esql thread unsafe - bug
Date Tue, 19 Feb 2002 19:02:08 GMT

I've discovered serious bug in esql logicsheet while using it with
cocoon-1.8.3. However the same bug seems to exists in cocoon2. The
problem is that while node stack logic variables (xspParentNode,
xspCurrentNode, xspNodeStack) are defined inside populateDocument
method, similar objects used by esql (_esql_connections etc...) exist as
object attributes.

Since there is only one instance of particular xsp page (eg.
_index.class) per application, under havy load it is possible (and easy
to observe using eg jmeter) that concurent calls to the same
_index.populateDocument method will lead esql structures and connection
pools to be corrupted.

you can find attached the patch that should fix thing up (it works at
least with cocoon-1.8.x)



View raw message