| 1 | ## Guidelines
|
| 2 |
|
| 3 | Firstly, if you are an Enterprise customer, you might want to head over to our [Customer Support Portal](http://support.neo4j.com/).
|
| 4 |
|
| 5 | If you think you might have **hit a bug** in our software (it happens occasionally!) or you have specific **feature request** then use the issue feature on the relevant GitHub repository.
|
| 6 | Check first though as someone else may have already raised something similar.
|
| 7 |
|
| 8 | If you simply want to get started or have a question on how to use a particular feature, ask a question in [Neo4j Online Community](https://community.neo4j.com/) instead.
|
| 9 | [StackOverflow](http://stackoverflow.com/questions/tagged/neo4j) also hosts a ton of questions and might already have a discussion around your problem.
|
| 10 | Make sure you have a look there too.
|
| 11 |
|
| 12 | If you want to make a feature request, please prefix your issue title with `[Feature Request]` so that it is clear to us.
|
| 13 | If you have a bug report however, please continue reading.
|
| 14 | To help us understand your issue, please specify important details, primarily:
|
| 15 |
|
| 16 | - Neo4j version: Community/Enterprise X.Y.Z
|
| 17 | - Neo4j Mode: Single instance/HA cluster with X members/Casual cluster with X core Y read-replica
|
| 18 | - Driver version: X lanaguage driver X.Y.Z (If you use some other library that wraps around this driver, you might want to raise an issue there first)
|
| 19 | - Operating system: (for example Windows 10/Ubuntu 16.10 on AWS)
|
| 20 | - **Steps to reproduce**
|
| 21 | - Expected behavior
|
| 22 | - Actual behavior
|
| 23 |
|
| 24 | Additionally, include (as appropriate) log-files, stacktraces, and other debug output.
|
| 25 | Always check the server logs to see if there is any stacktrace related to the driver error too.
|
| 26 | Aslo add any solutions you've tried to solve the problem yourself.
|
| 27 |
|
| 28 | ## Example bug report
|
| 29 |
|
| 30 | I got connection reset by peer errors.
|
| 31 |
|
| 32 | **Neo4j Version:** 3.4.10 Community
|
| 33 | **Neo4j Mode**: Single instance
|
| 34 | **Driver version**: JS driver 1.7.1
|
| 35 | **Operating System:** Ubuntu 16.10 on AWS
|
| 36 |
|
| 37 | ### Steps to reproduce
|
| 38 |
|
| 39 | 1. Start Neo4j on a AWS instance
|
| 40 | 2. Run a query with the driver
|
| 41 | 3. Put the driver idle for 2h
|
| 42 | 4. Run another query
|
| 43 |
|
| 44 | ### Expected behavior
|
| 45 |
|
| 46 | The second query shall run successfully
|
| 47 |
|
| 48 | ### Actual behavior
|
| 49 |
|
| 50 | The client failed to run the second query with a `connection reset by peer` stacktrace.
|
| 51 | _attach the stacktrace_
|
| 52 | Meanwhile, in the server log, I found this stacktrace that happened at the same time when the driver failed.
|
| 53 | _attach the stacktrace_
|