Return-Path: 
 <dev-return-58738-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 9866 invoked from network); 2 Apr 2004 01:32:46 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 2 Apr 2004 01:32:46 -0000
Received: (qmail 55422 invoked by uid 500); 2 Apr 2004 01:32:26 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 55363 invoked by uid 500); 2 Apr 2004 01:32:26 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 55349 invoked from network); 2 Apr 2004 01:32:25 -0000
Received: from unknown (HELO avocet.mail.pas.earthlink.net) (207.217.120.50)
  by daedalus.apache.org with SMTP; 2 Apr 2004 01:32:25 -0000
Received: from 1cust156.tnt3.barrie.on.da.uu.net ([66.48.153.156]
 helo=andrzej)
	by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1B9DXs-0007It-00; Thu, 01 Apr 2004 17:32:33 -0800
From: "Andrzej Jan Taramina" <andrzej@chaeron.com>
Organization: Chaeron Corporation
To: dev@cocoon.apache.org
Date: Thu, 01 Apr 2004 20:35:55 -0500
MIME-Version: 1.0
Subject: Re: Known concurrency issues in 2.1.4/JISP bugs....possible
 workaround?
Reply-to: andrzej@chaeron.com
CC: agallardo@agssa.net,
              bdelacretaz@codeconsult.ch,
              unico@hippo.nl
Message-ID: <406C7D2B.24481.1AEE6B31@localhost>
Priority: normal
In-reply-to: 
 <34515.10.0.0.5.1080666002.squirrel@ags01.agsoftware.dnsalias.com>
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Antonio suggested (and Bertrand/Unico also elaborated on this):

> > We're getting some sporadic strange errors that might be due to
> > concurrency
> > issues between different users, and I was wondering if there are any known
> > bugs outstanding in 2.1.4 for this kind of thing?
> 
> The problem can be the cache system:

Just a thought....if I have the following specified in my cocoon.xconf 
settings:

<transient-store logger="core.store.transient">
	<parameter name="maxobjects" value="@transient_object_cache_size@"/>
	<parameter name="use-persistent-cache" value="false"/>
</transient-store>
	
<store logger="core.store">
	<parameter name="maxobjects" value="@generic_object_cache_size@"/>
	<parameter name="use-persistent-cache" value="false"/>
</store>

Note: @xxx@ values are substituted using an Ant deploy script, so ignore that 
stuff.

With both having use-persistent-cache set to false, does that mean that JISP 
(the default persistent caching mechanism in 2.1.4) will never be called, and 
thus the concurrency errors should never manifest?

Or do I need to also do something to my persistent store config settings, 
which currently look like:

<persistent-store logger="core.store.persistent">
	<parameter name="use-cache-directory" value="true"/>
	<parameter name="order" value="2701"/>
</persistent-store>

An aside...what the heck is the "order" value anyway?

Much appreciate any insight on this, since we don't need persistent caching 
for our production application, and this might be a "quick fix" for a very 
vexing and difficult to reproduce problem.

Thanks all!

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com