Skip to content

Latest commit

 

History

History
48 lines (38 loc) · 2.35 KB

ISSUE_TEMPLATE.md

File metadata and controls

48 lines (38 loc) · 2.35 KB
Raw

Guidelines

Firstly, if you are an Enterprise customer, you might want to head over to our Customer Support Portal.

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. Check first though as someone else may have already raised something similar.

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 instead. StackOverflow also hosts a ton of questions and might already have a discussion around your problem. Make sure you have a look there too.

If you want to make a feature request, please prefix your issue title with [Feature Request] so that it is clear to us. If you have a bug report however, please continue reading.
To help us understand your issue, please specify important details, primarily:

  • Neo4j version: Community/Enterprise X.Y.Z
  • Neo4j Mode: Single instance/HA cluster with X members/Casual cluster with X core Y read-replica
  • Driver version: X language driver X.Y.Z (If you use some other library that wraps around this driver, you might want to raise an issue there first)
  • Operating system: (for example Windows 10/Ubuntu 16.10 on AWS)
  • Steps to reproduce
  • Expected behavior
  • Actual behavior

Additionally, include (as appropriate) log-files, stacktraces, and other debug output. Always check the server logs to see if there is any stacktrace related to the driver error too. Also, add any solutions you've tried to solve the problem yourself.

Example bug report

I got connection reset by peer errors.

Neo4j Version: 3.4.10 Community
Neo4j Mode: Single instance
Driver version: Java driver 1.7.1
Operating System: Ubuntu 16.10 on AWS

Steps to reproduce

  1. Start Neo4j on an AWS instance
  2. Run a query with the driver
  3. Put the driver idle for 2h
  4. Run another query

Expected behavior

The second query shall run successfully

Actual behavior

The client failed to run the second query with a connection reset by peer stacktrace.
attach the stacktrace
Meanwhile, in the server log, I found this stacktrace that happened at the same time when the driver failed.
attach the stacktrace