I clear the db. I pull down the latest snapshot using mvn -U.
Use that neo lib.
Still the same message.
/Björn
Johan Svensson wrote:
You sure you use the latest snapshot cause I didn't have that problem
when I tested on windows a few days ago?
I'll change the message but you will still get a recovery scan of the
logical log on next startup. If I get time I could try add an ugly
reflection hack that has been discussed on Sun's bugs forum as a
"workaround".
-Johan
On 11/6/07, Björn Granvik <[EMAIL PROTECTED]> wrote:
Hi guys (Johan),
When running Neo matrix example on Windows XP sp2, I get:
-------------------------------------------------
Hackers:
At depth 4 => The Architect
2007-nov-06 11:40:03 org.neo4j.impl.transaction.xaframework.XaLogicalLog
close
VARNING: Unable to delete clean logical log[db\nioneo_logical.log]
2007-nov-06 11:40:03 org.neo4j.impl.transaction.xaframework.XaLogicalLog
close
INFO: Since you're not using a real operating system you will be
punished for it at next startup
Process finished with exit code 0
-------------------------------------------------
Is there any way to avoid this problem? Probably not, since this is an
old issue with the logical log clean up on Windows.
Could there be a way with less apparent wording? :-)
Or should I go with logging on error level?
/Björn
_______________________________________________
Neo mailing list
User@lists.neo4j.org
http://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo mailing list
User@lists.neo4j.org
http://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo mailing list
User@lists.neo4j.org
http://lists.neo4j.org/mailman/listinfo/user
