<p dir="auto">My understanding is that <code class="notranslate">org.neo4j.server.transaction.timeout</code> is only for server mode.  I would like to request a timeout feature for embedded mode, to automatically abort any transaction longer than a given time.  Ideally this could be overridden in an individual transaction.  Previously we used the recommendation here: <a href="http://www.markhneedham.com/blog/2013/10/17/neo4j-setting-query-timeout/" rel="nofollow">http://www.markhneedham.com/blog/2013/10/17/neo4j-setting-query-timeout/</a>   however, from the author's update comment, it seems this no longer works in Neo4j 2.2+.  Maybe the execution guard function was removed? The timeout workaround we constructed in our own code (following that blog post, in an earlier Neo4j) does seem broken on Neo4j 2.3+.  So we no longer have a way to catch runaway queries, as far as I know.<br>
For comparison: Postgres <code class="notranslate">statement_timeout</code>  <a href="http://www.postgresql.org/docs/9.3/static/runtime-config-client.html" rel="nofollow">http://www.postgresql.org/docs/9.3/static/runtime-config-client.html</a></p>
<p dir="auto">I am using Java API in an embedded graph (version 1.9.4) and using the following code to get the ShortestPath -<br>
GraphAlgoFactory.shortestPath(expander, 15)<br>
where expander is a expander with specific relationship types.</p>
<p dir="auto">In rare cases, the graph (which is about 28 G on a JVM sized to 10G) just spins for more than 30 minutes. Is there a way to specify the timeout so that shortestPath query is cancelled?</p>