You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Andrzej Jan Taramina <an...@chaeron.com> on 2004/04/20 15:18:50 UTC

Modular Database Action query caching inoperative....bug....

I've posted this as bug #28495.

In org.apache.cocoon.acting.modular.DatabaseAction, the implemented query 
caching is inoperative.

In the processTable() method a new LookUpKey is created for every request, 
and since the equals/hashKey methods are not overriden in LookUpKey, this 
means that the getQuery() method will be called for all requests and no 
caching is used, since the HashMap get will always  
return null.

Found this trying to hunt down a nasty concurrency bug (manifesting in 2.1.4) 
where the data being written to the database seems to be using another 
sessions values intermittently.

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


Re: Modular Database Action query caching inoperative....bug....

Posted by Tuomo L <tl...@cc.hut.fi>.
Does this possibly fix this too? Haven't gotten any replies on this yet...
:(

It'd be nice, if someone could at least try it out, if it works or not.

http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108272532719287&w=2

-Tuomo

On Wed, 28 Apr 2004, Christian Haul wrote:

> Christian Haul wrote:
> > Andrzej Jan Taramina wrote:
> >
> >> I've posted this as bug #28495.
> >>
> >> In org.apache.cocoon.acting.modular.DatabaseAction, the implemented
> >> query caching is inoperative.
> >>
> >> In the processTable() method a new LookUpKey is created for every
> >> request, and since the equals/hashKey methods are not overriden in
> >> LookUpKey, this means that the getQuery() method will be called for
> >> all requests and no caching is used, since the HashMap get will
> >> always  return null.
> >>
> >> Found this trying to hunt down a nasty concurrency bug (manifesting in
> >> 2.1.4) where the data being written to the database seems to be using
> >> another sessions values intermittently.
> >>
> >> Andrzej Jan Taramina
> >> Chaeron Corporation: Enterprise System Solutions
> >> http://www.chaeron.com
> >
> >
> > Thanks for reporting. Will take care of this.
>
> Sorry for the delay. Anyway, this should be fixed in CVS. Please
> cross-check and report back.
>
> 	Chris.
>

Re: Modular Database Action query caching inoperative....bug....

Posted by Christian Haul <ha...@informatik.tu-darmstadt.de>.
Christian Haul wrote:
> Andrzej Jan Taramina wrote:
> 
>> I've posted this as bug #28495.
>>
>> In org.apache.cocoon.acting.modular.DatabaseAction, the implemented 
>> query caching is inoperative.
>>
>> In the processTable() method a new LookUpKey is created for every 
>> request, and since the equals/hashKey methods are not overriden in 
>> LookUpKey, this means that the getQuery() method will be called for 
>> all requests and no caching is used, since the HashMap get will 
>> always  return null.
>>
>> Found this trying to hunt down a nasty concurrency bug (manifesting in 
>> 2.1.4) where the data being written to the database seems to be using 
>> another sessions values intermittently.
>>
>> Andrzej Jan Taramina
>> Chaeron Corporation: Enterprise System Solutions
>> http://www.chaeron.com
> 
> 
> Thanks for reporting. Will take care of this.

Sorry for the delay. Anyway, this should be fixed in CVS. Please
cross-check and report back.

	Chris.

Re: Modular Database Action query caching inoperative....bug....

Posted by Christian Haul <ha...@informatik.tu-darmstadt.de>.
Andrzej Jan Taramina wrote:
> I've posted this as bug #28495.
> 
> In org.apache.cocoon.acting.modular.DatabaseAction, the implemented query 
> caching is inoperative.
> 
> In the processTable() method a new LookUpKey is created for every request, 
> and since the equals/hashKey methods are not overriden in LookUpKey, this 
> means that the getQuery() method will be called for all requests and no 
> caching is used, since the HashMap get will always  
> return null.
> 
> Found this trying to hunt down a nasty concurrency bug (manifesting in 2.1.4) 
> where the data being written to the database seems to be using another 
> sessions values intermittently.
> 
> Andrzej Jan Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com

Thanks for reporting. Will take care of this.

	Chris.