When I run testing connection in Management/Datasources to a Neo4J db called MVP, I am getting the following error:
Datasources Configuration Editor: Could not validate datasource [MVP]. {“error”:{“root_cause”:[{“type”:“exception”,“reason”:“Could not validate datasource [MVP].”}],“type”:“exception”,“reason”:“Could not validate datasource [MVP].”,“caused_by”:{“type”:“s_q_l_transient_connection_exception”,“reason”:“MVP-pool - Connection is not available, request timed out after 30107ms.”}},“status”:500}
Thanks
Hello Julia,
Could you post the corresponding Elasticsearch logs due to this error?
Regards,
Varun
Datasources Configuration Editor: Could not validate datasource [MVP]. {“error”:{“root_cause”:[{“type”:“exception”,“reason”:“Could not validate datasource [MVP].”}],“type”:“exception”,“reason”:“Could not validate datasource [MVP].”,“caused_by”:{“type”:“s_q_l_transient_connection_exception”,“reason”:“MVP-pool - Connection is not available, request timed out after 30072ms.”}},“status”:500}
Log:
Desired survivor size 17432576 bytes, new threshold 6 (max 6)
- age 1: 1468672 bytes, 1468672 total
- age 2: 970248 bytes, 2438920 total
- age 3: 144 bytes, 2439064 total
: 276695K->3703K(306688K), 0.0097393 secs] 488722K->215730K(1014528K), 0.0099860 secs] [Times: user=0.02 sys=0.00, real=0.01 secs]
2019-07-26T19:47:24.452+0000: 161844.375: Total time for which application threads were stopped: 0.0107449 seconds, Stopping threads took: 0.0003111 seconds
2019-07-26T19:47:25.453+0000: 161845.376: Total time for which application threads were stopped: 0.0004629 seconds, Stopping threads took: 0.0000743 seconds
2019-07-26T19:47:28.455+0000: 161848.377: Total time for which application threads were stopped: 0.0003653 seconds, Stopping threads took: 0.0000709 seconds
2019-07-26T19:47:32.994+0000: 161852.916: Total time for which application threads were stopped: 0.0003864 seconds, Stopping threads took: 0.0000692 seconds
2019-07-26T19:47:32.994+0000: 161852.916: Total time for which application threads were stopped: 0.0001865 seconds, Stopping threads took: 0.0000355 seconds
2019-07-26T19:47:32.994+0000: 161852.917: Total time for which application threads were stopped: 0.0001636 seconds, Stopping threads took: 0.0000216 seconds
2019-07-26T19:47:32.995+0000: 161852.917: Total time for which application threads were stopped: 0.0002108 seconds, Stopping threads took: 0.0000372 seconds
2019-07-26T19:47:32.995+0000: 161852.918: Total time for which application threads were stopped: 0.0002340 seconds, Stopping threads took: 0.0000483 seconds
2019-07-26T19:47:32.995+0000: 161852.919: Total time for which application threads were stopped: 0.0001611 seconds, Stopping threads took: 0.0000250 seconds
2019-07-26T19:47:32.998+0000: 161852.921: Total time for which application threads were stopped: 0.0002006 seconds, Stopping threads took: 0.0000373 seconds
2019-07-26T19:47:33.000+0000: 161852.922: Total time for which application threads were stopped: 0.0002079 seconds, Stopping threads took: 0.0000413 seconds
2019-07-26T19:47:33.036+0000: 161852.959: Total time for which application threads were stopped: 0.0003314 seconds, Stopping threads took: 0.0000669 seconds
2019-07-26T19:47:33.037+0000: 161852.960: Total time for which application threads were stopped: 0.0004717 seconds, Stopping threads took: 0.0000703 seconds
2019-07-26T19:47:33.037+0000: 161852.960: Total time for which application threads were stopped: 0.0001977 seconds, Stopping threads took: 0.0000664 seconds
2019-07-26T19:47:36.039+0000: 161855.962: Total time for which application threads were stopped: 0.0003665 seconds, Stopping threads took: 0.0000735 seconds
2019-07-26T19:47:37.806+0000: 161857.729: Total time for which application threads were stopped: 0.0008515 seconds, Stopping threads took: 0.0000663 seconds
2019-07-26T19:47:51.822+0000: 161871.744: Total time for which application threads were stopped: 0.0003614 seconds, Stopping threads took: 0.0000759 seconds
2019-07-26T19:47:53.823+0000: 161873.745: Total time for which application threads were stopped: 0.0003559 seconds, Stopping threads took: 0.0000681 seconds
2019-07-26T19:48:03.828+0000: 161883.750: Total time for which application threads were stopped: 0.0003184 seconds, Stopping threads took: 0.0000731 seconds
2019-07-26T19:48:15.842+0000: 161895.764: Total time for which application threads were stopped: 0.0003120 seconds, Stopping threads took: 0.0000642 seconds
2019-07-26T19:48:25.865+0000: 161905.787: Total time for which application threads were stopped: 0.0008403 seconds, Stopping threads took: 0.0000635 seconds
2019-07-26T19:48:30.722+0000: 161910.644: Total time for which application threads were stopped: 0.0003189 seconds, Stopping threads took: 0.0000649 seconds
2019-07-26T19:48:31.345+0000: 161911.267: Total time for which application threads were stopped: 0.0004701 seconds, Stopping threads took: 0.0000813 seconds
2019-07-26T19:48:34.347+0000: 161914.268: Total time for which application threads were stopped: 0.0003345 seconds, Stopping threads took: 0.0000782 seconds
2019-07-26T19:48:53.003+0000: 161932.925: Total time for which application threads were stopped: 0.0003392 seconds, Stopping threads took: 0.0000696 seconds
2019-07-26T19:48:53.005+0000: 161932.926: Total time for which application threads were stopped: 0.0003638 seconds, Stopping threads took: 0.0001307 seconds
2019-07-26T19:
and as expected
node app
also generates errors. Let me know if you want to see them as well
Yes, please. Are there any more logs in elasticsearch?
anything in particular you are looking for?
Hi Varun.
I would like to resolve this as soon as possible. My client is evaluating a number of options for their application and how easy it is to install is one of the big considerations.
What information can I provide?
Julia
Hello Julia,
It appears that the Federate connector is not able to connect to Neo4J, logs from Elasticsearch would help ascertain the issue. The above provided logs seem to be monitoring logs rather than Elasticsearch. How have you configured Neo4J? A dummy (Working) Neo4J configuration for the jdbc connector looks like this:
It would be advisable to Test the Datasource connection before going through with the process of Neo4j import.
Regards,
Varun
1 Like
When I run testing connection in Management/Datasources to a Neo4J db called MVP, I am getting the following error:
Datasources Configuration Editor: Could not validate datasource [MVP]. {“error”:{“root_cause”:[{“type”:“exception”,“reason”:“Could not validate datasource [MVP].”}],“type”:“exception”,“reason”:“Could not validate datasource [MVP].”,“caused_by”:{“type”:“s_q_l_transient_connection_exception”,“reason”:“MVP-pool - Connection is not available, request timed out after 30107ms.”}},“status”:500}
Thanks
Hi Julia,
The timeout error may be caused by the fact that the ElasticSearch server is not able to reach the NEO4J server (due to firewall rules, network issues or a wrong connection URL).
Can you check the connection string you are using ?
You may have a look at the current NEO4J documentation:
http://neo4j-contrib.github.io/neo4j-jdbc/
We currently support the HTTP protocol. So, you connection string should look like this:
jdbc:neo4j:http://<host>:<port>/
You may also test from your ElasticSearch server if the Neo4J server is reachable. A typical telnet command should do the job. Typically from a terminal:
telnet myneo4jservername 7474
Notice that the port is not a standard HTTP port. By default, Neo4J is using 7474:
https://neo4j.com/docs/operations-manual/current/configuration/ports/
You should check which port is currently in use in your current configuration.
Let me know.
1 Like
