It looks like previously working approach is deprecated now:

```
unsupported.dbms.executiontime_limit.enabled=true
unsupported.dbms.executiontime_limit.time=1s

```

According to the [documentation](http://neo4j.com/docs/operations-manual/current/reference/) new variables are responsible for timeouts handling:

```
dbms.transaction.timeout
dbms.transaction_timeout

```

At the same time the new variables look related to the transactions. 

The new timeout variables look not working. They were set in the neo4j.conf as follows:

```
dbms.transaction_timeout=5s
dbms.transaction.timeout=5s

```

Slow cypher query isn't terminated. 

Then the Neo4j plugin was added to model a slow query with transaction:

```
    @Procedure("test.slowQuery")
    public Stream<Res> slowQuery(@Name("delay") Number Delay )
    {
        ArrayList<Res> res = new ArrayList<>();

        try ( Transaction tx = db.beginTx() ){
            Thread.sleep(Delay.intValue(), 0);
            tx.success();
        } catch (Exception e) {
            System.out.println(e);
        }

        return res.stream();
    }

```

The function served by the plugin is executed with neoism Golang package. And the timeout isn't triggered as well.