cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Howard <>
Subject Re: DO NOT REPLY [Bug 26753] - Persistent store or cache corruption?
Date Sun, 08 Feb 2004 19:01:32 GMT
Carsten Ziegeler wrote:

> Geoff Howard wrote:
>>I didn't realize this was not a universal problem.  The impression I had 
>>was that this was consistently repeatable given the same actions in any 
> Oh, ok - this might be, perhaps I'm wrong. I didn't try it, but it looked
> for me like a problem we faced several months ago with Jisp. It was
> exactly the same behaviour (garbage served from the cache in combination
> with the exception msg).
> I then contacted Scott, the author of Jisp directly, and told him
> the problem. He answered that this is a known issues and that it will be
> fixed with the next release which is now the 3.0 release.
>>Carsten, as I can't find any information on the Jisp aspect of this, do 
>>you have any links or hints where to find clues on the environment 
>>dependencies?  If this is limited to an OS or JDK version, it would be 
>>very helpful to consider that.
> The only thing I can say is that we had these problems with different JDK
> versions (don't ask me which were really tested) from Sun and Suse Linux.
> It was very hard to reproduce the problem, it just happened from time
> to time and we never had the problems on different installations.
>>>From our experience it seems (though this might be wrong), that this only
> happens on Linux in a certain configuration. We have other installations
> with the same JDK, the same Linux version and the exception never occurs.

Hmmm.  Ok - unfortunately, coyotegulch (jisp) site is down at the moment 
so tracking this all down is going to have to wait.

I wanted to at least try swapping in 3.0 to see how bad the issues of an 
upgrade would be.  I also wanted to investigate the feasibility of a 
back-port of the fix.  Anyone already done this?


View raw message