Hi,
I have a problem in category "query should return something, but it doesn't",
too.
One subnode of the rep does not seem to be reachable anymore by xpath queries.
The problem exists since I shut down my app, and temporarely startet magnolia.
But I frankly cannot imagine that this can cause a problem of this sort.
The situation is as follows:
/
A (nt:unstructured)
A1 (nt:unstructured)
A2 (nt:unstructured)
B (nt:unstructured)
B1 (nt:unstructured)
B2 (nt:unstructured)
The problem is that no query in the /A substree works anymore. They all return
empty, including statements that have worked for months. Finally, I tested
something like this:
//element(*, nt:unstructed)
This query returns all nt:unstructured nodes of B, but not of A! The behaviour
is the same for both, application and query tools. I already rebuilt the index,
but the effect is still the same.
Question: could there be a Lucene internal lock? I consider that unlikely, the
rebuild would have solved the problem. Or is there an inconcistence in the JCR
that makes a correct indexing impossible? Also unlikely, as the node tree of A
can be navigated without a problem through the JCR API.
Thus, I'm pretty clouless. Anybody with an idea?
Regards,
Juerg
