(Bolt) Use of ServiceUnavailableException in TLS-enabled channel

[nandosola]

Hi,

I'm trying to debug a potential issue in neo4j-ogm that might be related to Bolt session handling after a server restart (see also: spring-projects/spring-data-neo4j#373). Before going any further, I have a doubt concerning the Java Driver:

• For plaintext connections, the first operation after the restart results in a ServiceUnavailableException with the following message:

  "Connection terminated while receiving data. This can happen due to network instabilities, or due to restarts of the database."

• For TLS-enabled connections, the first operation after the restart results in a ClientException with exactly the same message.

My question is, why are there two different exceptions instead of just using ServiceUnavailableException for both?

---

Just FYI, neo4j-ogm doesn't handle ServiceUnavailableException yet. It just wraps ClientExceptions coming from server disconnections or network glitches in CypherException, so the library user has to catch them and reconnect manually, invoking a new query.

[zhenlineo]

We will have a look at this. It should be a ServiceUnavailable for TLS connection too by reading directly.

[zhenlineo]

The bug should have been fixed and released in 1.1.2 driver. I am closing this issue but pls let me know if the problem still exists.