Hi All,
having wasted quite some time on it, here's what I have found:
- multiple threads accessing the contentIterator method (and
JCRExpressionStore in general) at the same time. -> I've added sync
blocks (looks like it's fixing it)
- context was indeed not set, (am now setting it when reading an
expression) and I think the original exception has disappeared now.
- the contentiterator method is using a lot of resources, time and
memory. I agree with John that we should re-implement that method
quickly.
Can somebody in the magnolia devs, check the current trunk, and give
me feedback ?
Also, on shutdown, things are going a bit crazy. I get concurrent
access exception traces, and I'm not sure the openwfe store is kept
in a stable state. Can somebody have a look.
It's almost time for me to go home ... but I'd stay here a bit if
somebody have some ideas/can help.
Nicolas,
On May 18, 2006, at 5:35 PM, John Mettraux wrote:
On 5/18/06, Nicolas <[email protected]> wrote:
Looks like it's coming from a deleted node in the repository, but the
workflow engine does not know about it.
Hi Nicolas,
very interesting : how are the two logs interrelated, are they taken
from the same log file ?
You're saying that this doesn't seem to affect the engine's operation,
aren't you ?
I'd love to reimplement the contentIterator of the JCRExpressionStore.
Under very heavy load (lots of processes dehydrated), it might break.
See the attached FileExpressionStore.java (sorry, sf.net's webSvn is
down), it contains a StoreIterator which doesn't fill up the memory
when iterating over the content of the pool. I think it's no big deal
adapting that to the JCRExpressionStore as this store concepts are
pretty much the same as the ones of the FileExpressionStore.
WDYT ?
John
<FileExpressionStore.java>
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
