Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Creating/closing a driver takes a long time

See original GitHub issue

Neo4j version: Community Neo4j 3.5.3
Neo4j Mode: Single instance
Driver version: Java language driver 1.7.2
Operating system: Ubuntu 18.04.2 LTS
Steps to reproduce

Start local instance of Neo4j 3.5.3
Run the following class

import org.neo4j.driver.v1.*;

public class DriverTest {
    public static void main(String[] args) {
        long start = System.currentTimeMillis();
        Driver driver = GraphDatabase.driver("bolt://localhost:7687", AuthTokens.basic("neo4j", "hej"));
        long created = System.currentTimeMillis();
        driver.close();
        long closed = System.currentTimeMillis();
        System.out.println("creation: " + (created - start) + "ms");
        System.out.println("closing: " + (closed - created) + "ms");
    }
}

Expected behavior

creation: 14ms
closing: 22ms

Actual behavior

creation: 1478ms
closing: 2248ms

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:13 (5 by maintainers)

Top GitHub Comments

3reactions

zhenlineocommented, Jul 1, 2019

Hi @kant111 The close blocking for too long problem has been fix in 2.0 with this PR https://github.com/neo4j/neo4j-java-driver/pull/576. For the driver creation takes too long problem, it will be fixed in this PR https://github.com/neo4j/neo4j-java-driver/pull/609, where you can choose to turn off the connectivity verification on driver creation to avoid a network round trip.

As they are behaviour changes, they will not be back ported to 1.7 drivers.

0reactions

technigecommented, Jan 2, 2020

Closing issue as this has been addressed in #576 and #609.