Hi,
I added a comment on the ticket. The problem is (as pointed out in the
comment) the join performed from thread 1 (main) on thread 2. If that
is removed both transactions will complete (no deadlock).
Regards,
-Johan
On Thu, Nov 12, 2009 at 2:08 PM, Daniel MartÃnez
wrote:
> Ok, I created a ti
Thanks, there seems to be some known problems with lucene on NFS. If
you're calling getNodes on a non-existing index then I committed a fix
for that (added one extra null check), but if that index should exist
it could just be that lucene is having trouble with NFS.
I'll look into this further to
I had an answer for this also, but see that Andreas and Anders have both
answered with the two mechanisms I had tried:
- lucene
- custom index
But I thought I'd add a little on the custom index idea, because I think
that can also provide fast sorting, if you are usually requiring answers in
Mattias Persson schrieb:
>>> After playing with it more, the culprit seems to be not the symbolic
>>> link but the local drive :-/ When I delete the neo4j directory with the
>>> db and start the application from the local drive then I'm getting the
>>> NPEs - even if I shut the server down and star
>> After playing with it more, the culprit seems to be not the symbolic
>> link but the local drive :-/ When I delete the neo4j directory with the
>> db and start the application from the local drive then I'm getting the
>> NPEs - even if I shut the server down and start it again. When I delete
>>
5 matches
Mail list logo
