I tried with the -config and same problem. I did some more tinkering including setting time to 1000b and encountered a parameter formatting error on neo4j server startup as expected.
Maybe this was just confusion on my part. I assumed time is in ms, so 1000 would be 1 second, etc. But it works if I set value in seconds (e.g., 1, 2, 5, etc). I did a lot of testing and it is definitely working in seconds on my system: *org.neo4j.server.webserver.limit.executiontime=5 (times out if my query runs longer than 5 seconds).* *org.neo4j.server.webserver.limit.executiontime=10 (times out if my query runs longer than 10 seconds).* ********* neo4j-sh (?)$ match n-[r]-() return distinct labels(n), type(r); ==> GuardTimeoutException: timeout occured (overtime=1) neo4j-sh (?)$ ******* *Thanks, Dan* On Thursday, May 7, 2015 at 9:24:24 PM UTC-4, Sumit Gupta wrote: > Guard works with community version too. > > can you try using neo4jshell with "-config". My best guess is that it is > not picking up the property. > > Thanks, > Sumit > > On Thursday, 7 May 2015 06:16:00 UTC+5:30, Dan wrote: >> >> Hello, >> >> I have a question about enabling the query timeout option in neo4j 2.2.0 >> >> I added this to my neo4j.properties file: >> >> *execution_guard_enabled=true* >> >> And I added this line to my neo4j-server.properties file: >> >> *org.neo4j.server.webserver.limit.executiontime=1000* >> >> But when I run queries no timeout occurs as expected if they exceed 1 >> second. I'm running my queries in the neo4j web interface. >> >> I have no clue what I could be doing wrong. Or does this feature not >> apply when running queries in web interface? >> >> I have tried this on windows and also a Linux deployment with same >> results. >> >> Thanks, Dan >> > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
