So I've now checked all my code for correct dealing of
InterruptedException also :)
It occurred to me it would be wise for you to log the interrupted
exception before clearing the status. Otherwise later on you'll be
wondering why a thread just quitted in the middle of a method, no?
I've ju
On 8 Jun 2009, at 14:24, Johan Svensson wrote:
> On Mon, Jun 8, 2009 at 1:42 PM, Neil Ellis
> wrote:
>> On 8 Jun 2009, at 12:21, Johan Svensson wrote:
>>> On Mon, Jun 8, 2009 at 12:04 PM, Neil Ellis
>>> wrote:
So after a weekend away from the problem it occured to me that I
had
>>
On Mon, Jun 8, 2009 at 1:42 PM, Neil Ellis wrote:
> On 8 Jun 2009, at 12:21, Johan Svensson wrote:
>> On Mon, Jun 8, 2009 at 12:04 PM, Neil Ellis
>> wrote:
>>> So after a weekend away from the problem it occured to me that I had
>>> neglected to nohup the java process. Therefore I am suspect that
Antonello,
Just thought I'd mention that trunk now has support for non memory
mapped buffers. When starting Neo4j just pass in:
use_memory_mapped_buffers=false
as a parameter to the public EmbeddedNeo( String storeDir,
Map params ) constructor.
The code of plain buffer/direct buffer ports of pr
On 8 Jun 2009, at 12:21, Johan Svensson wrote:
> On Mon, Jun 8, 2009 at 12:04 PM, Neil Ellis
> wrote:
>> So after a weekend away from the problem it occured to me that I had
>> neglected to nohup the java process. Therefore I am suspect that was
>> the problem, running now with nohup ;-)
>>
>
On Mon, Jun 8, 2009 at 12:04 PM, Neil Ellis wrote:
> So after a weekend away from the problem it occured to me that I had
> neglected to nohup the java process. Therefore I am suspect that was
> the problem, running now with nohup ;-)
>
Lets hope this works. I am not 100% sure about this but norm
So after a weekend away from the problem it occured to me that I had
neglected to nohup the java process. Therefore I am suspect that was
the problem, running now with nohup ;-)
It also occured to me that on receipt of ClosedByInterruptException
Neo4J should probably trigger a shutdown (i.e.
Yes,
Currently the reference node always has node id 0 but this may change
in the future. We currently have some discussions about making the
reference node static so you can't delete it (will then always be
there with id 0). Another solution that has been discussed is to have
a setReferenceNode m
8 matches
Mail list logo