You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Helena Edelson <he...@greenjaguar.com> on 2006/03/08 01:02:54 UTC
cache insight?
Hi,
I have been running into a cache issue I think.
Even if I shutdown jetty, delete the cache, run forrest clean,
reboot my machine, restart jetty, run localhost in an new browser window
or even a different browser program,
changes to various xsl file I am working on are not reflected.
Somehow Jetty or something else holds on to an older iteration of the
xsl file.
This has happened lately even with changes to xml data files, something
was holding onto
several iterations previous of the file's data.
Logs say nothing indicative except:
WARN (2006-03-07) 18:28.40:136 [core.manager]
(/articles/photoessays/yosemite_sar.html)
PoolThread-4/CoreServiceManager: disposing of handler for unreleased
component. role
[org.apache.cocoon.components.treeprocessor.ProcessorComponentInfo]
Anyone have insight or solved this themselves?
helena
Re: cache insight?
Posted by Helena Edelson <he...@greenjaguar.com>.
David Crossley wrote:
>Helena Edelson wrote:
>
>
>>Hi,
>>I have been running into a cache issue I think.
>>
>>
>
>Did you solve the previous issue that you asked
>for help with. It seemed that you had a fundamental
>installation issue, but you didn't say whether our
>feedback helped you.
>
>
>
Yes, forrest clean worked. Thank you. I have used that before
but simply forgot.
>>Even if I shutdown jetty, delete the cache, run forrest clean,
>>reboot my machine, restart jetty, run localhost in an new browser window
>>or even a different browser program,
>>changes to various xsl file I am working on are not reflected.
>>Somehow Jetty or something else holds on to an older iteration of the
>>xsl file.
>>This has happened lately even with changes to xml data files, something
>>was holding onto
>>several iterations previous of the file's data.
>>Logs say nothing indicative except:
>>WARN (2006-03-07) 18:28.40:136 [core.manager]
>>(/articles/photoessays/yosemite_sar.html)
>>PoolThread-4/CoreServiceManager: disposing of handler for unreleased
>>component. role
>>[org.apache.cocoon.components.treeprocessor.ProcessorComponentInfo]
>>
>>
>
>I don't think that that log message is related.
>
>-David
>
>
>
>>Anyone have insight or solved this themselves?
>>
>>helena
>>
>>
>
>
>
>
Re: cache insight?
Posted by David Crossley <cr...@apache.org>.
Helena Edelson wrote:
> Hi,
> I have been running into a cache issue I think.
Did you solve the previous issue that you asked
for help with. It seemed that you had a fundamental
installation issue, but you didn't say whether our
feedback helped you.
> Even if I shutdown jetty, delete the cache, run forrest clean,
> reboot my machine, restart jetty, run localhost in an new browser window
> or even a different browser program,
> changes to various xsl file I am working on are not reflected.
> Somehow Jetty or something else holds on to an older iteration of the
> xsl file.
> This has happened lately even with changes to xml data files, something
> was holding onto
> several iterations previous of the file's data.
> Logs say nothing indicative except:
> WARN (2006-03-07) 18:28.40:136 [core.manager]
> (/articles/photoessays/yosemite_sar.html)
> PoolThread-4/CoreServiceManager: disposing of handler for unreleased
> component. role
> [org.apache.cocoon.components.treeprocessor.ProcessorComponentInfo]
I don't think that that log message is related.
-David
> Anyone have insight or solved this themselves?
>
> helena
Re: cache insight?
Posted by Tim Williams <wi...@gmail.com>.
On 3/8/06, Thorsten Scherler <th...@wyona.com> wrote:
> El mar, 07-03-2006 a las 19:02 -0500, Helena Edelson escribió:
> > Hi,
> > I have been running into a cache issue I think.
> > Even if I shutdown jetty, delete the cache, run forrest clean,
> > reboot my machine, restart jetty, run localhost in an new browser window
> > or even a different browser program,
> > changes to various xsl file I am working on are not reflected.
>
> Are you using custom pipes or as well the default pipes are working like
> this?
>
> Did you activated the profiling?
>
> > Somehow Jetty or something else holds on to an older iteration of the
> > xsl file.
>
> Wich version of forrest?
>
> > This has happened lately even with changes to xml data files, something
> > was holding onto
> > several iterations previous of the file's data.
> > Logs say nothing indicative except:
> > WARN (2006-03-07) 18:28.40:136 [core.manager]
> > (/articles/photoessays/yosemite_sar.html)
> > PoolThread-4/CoreServiceManager: disposing of handler for unreleased
> > component. role
> > [org.apache.cocoon.components.treeprocessor.ProcessorComponentInfo]
> >
> > Anyone have insight or solved this themselves?
> >
>
> Hmm, I had caching issues only with the lm and dispatcher when adding
> new contracts but nothing that a restart and build clean would not heal.
Thorsten, I'm sure you figured this out by now, but the other day when
I was playing around with dispatcher, I had to just turn lm caching
off in forrest.xconf and it sped the cycle up -- though slowed forrest
down in general;)
I'm hoping that this will be fixed by the end of Forrest Friday - in
playing with dispatcher, I realized what a pain it is.
--tim
Re: cache insight?
Posted by Thorsten Scherler <th...@wyona.com>.
El mar, 07-03-2006 a las 19:02 -0500, Helena Edelson escribió:
> Hi,
> I have been running into a cache issue I think.
> Even if I shutdown jetty, delete the cache, run forrest clean,
> reboot my machine, restart jetty, run localhost in an new browser window
> or even a different browser program,
> changes to various xsl file I am working on are not reflected.
Are you using custom pipes or as well the default pipes are working like
this?
Did you activated the profiling?
> Somehow Jetty or something else holds on to an older iteration of the
> xsl file.
Wich version of forrest?
> This has happened lately even with changes to xml data files, something
> was holding onto
> several iterations previous of the file's data.
> Logs say nothing indicative except:
> WARN (2006-03-07) 18:28.40:136 [core.manager]
> (/articles/photoessays/yosemite_sar.html)
> PoolThread-4/CoreServiceManager: disposing of handler for unreleased
> component. role
> [org.apache.cocoon.components.treeprocessor.ProcessorComponentInfo]
>
> Anyone have insight or solved this themselves?
>
Hmm, I had caching issues only with the lm and dispatcher when adding
new contracts but nothing that a restart and build clean would not heal.
Are you sure that you edit the right project (may sound silly but it was
many times my problem when I found problems like you describe)? ;)
> helena
HTH
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org