Skip to content

Commit 87645d8

Browse files
renetapopovarenetapopova
committed
update connection exception errors
1 parent ddb389d commit 87645d8

File tree

3 files changed

+149
-155
lines changed

3 files changed

+149
-155
lines changed

‎modules/ROOT/pages/errors/gql-errors.adoc‎

Lines changed: 63 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,8 @@
33
[[neo4j-gqlstatus-errors]]
44
= List of all GQLSTATUS server error codes
55

6-
The following page provides an overview of all server errors in Neo4j, along with some scenarios and their possible solutions.
6+
//The following page provides an overview of all server errors in Neo4j, along with some scenarios and their possible solutions.
7+
The following page provides an overview of all GQLSTATUS server error codes in Neo4j.
78
All errors in Neo4j have severity level `ERROR`.
89

910
* <<_connection-exceptions, Connection exceptions>>
@@ -12,96 +13,88 @@ All errors in Neo4j have severity level `ERROR`.
1213
[[_connection-exceptions]]
1314
== Connection exceptions
1415

15-
The following is a list of the connection exceptions that can occur in Neo4j.
16+
Connection exceptions occur when the client is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.
1617

1718
=== 08000
1819

19-
Notifies the client that an exception occurred during the connection.
20-
21-
.Error details
22-
[cols="<1s,<4"]
23-
|===
24-
|GQLSTATUS code
25-
m|0800
26-
|Status description
27-
a|error: connection exception
28-
|Classification
29-
m|CLIENT_ERROR
30-
|===
20+
Status description:: error: connection exception
3121

3222
=== 08007
3323

34-
Notifies the client that an exception occurred during the resolution of a transaction.
35-
36-
.Error details
37-
[cols="<1s,<4"]
38-
|===
39-
|GQLSTATUS code
40-
m|08007
41-
|Status description
42-
|error: connection exception - transaction resolution unknown.
43-
|Classification
44-
m|CLIENT_ERROR
45-
|===
24+
Status description:: error: connection exception - transaction resolution unknown
4625

4726
=== 08N00
4827

49-
Notifies the client that an exception occurred while trying to connect to a specified database.
28+
Status description:: error: connection exception - unable to connect to database. Unable to connect to database { $db }. Unable to get bolt address of the leader. Check the status of the database. Retrying your request at a later time may succeed.
5029

51-
.Error details
52-
[cols="<1s,<4"]
53-
|===
54-
|GQLSTATUS code
55-
m|08N00
56-
|Status description
57-
a|error: connection exception - unable to connect to database. Unable to connect to database `$db`. Unable to get bolt address of the leader. Check the status of the database. Retrying your request at a later time may succeed.
58-
|Classification
59-
m|CLIENT_ERROR
60-
|===
6130

6231
=== 08N01
6332

64-
Notifies the client that an exception occurred while trying to write to a specified database.
33+
Status description:: error: connection exception - unable to write to database. Unable to write to database { $db } on this server. Server-side routing is disabled. Either connect to the database leader directly or enable server-side routing by setting '{ $cfgSetting }=true'.
6534

66-
.Error details
67-
[cols="<1s,<4"]
68-
|===
69-
|GQLSTATUS code
70-
m|08N01
71-
|Status description
72-
a|error: connection exception - unable to write to database. Unable to write to database `$db` on this server. Server-side routing is disabled. Either connect to the database leader directly or enable server-side routing by setting `$cfgSetting=true`.
73-
|Classification
74-
m|CLIENT_ERROR
75-
|===
35+
//Possible solutions:
36+
//Either connect to the database directly using the driver or interactively with the `:use { $db }` command), or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
7637

7738
=== 08N02
7839

79-
Notifies the client that an exception occurred while trying to connect to a specified database.
40+
Status description:: error: connection exception - unable to write to database. Unable to connect to database { $db }. Server-side routing is disabled. Either connect to { $db } directly, or enable server-side routing by setting '{ $cfgSetting }=true'.
8041

81-
.Error details
82-
[cols="<1s,<4"]
83-
|===
84-
|GQLSTATUS code
85-
m|08N02
86-
|Status description
87-
a|error: connection exception - unable to route to database. Unable to connect to database `$db`. Server-side routing is disabled. Either connect to `$db` directly, or enable server-side routing by setting `$cfgSetting=true`.
88-
|Classification
89-
m|CLIENT_ERROR
90-
|===
42+
Example error description:: error: connection exception - unable to route to database. Unable to connect to database `my_db`. Server-side routing is disabled. Either connect to `my_db` directly, or enable server-side routing by setting 'dbms.routing.enabled=true'.
43+
44+
//Possible solutions:
45+
//Either connect to the database directly using the driver or interactively with the `:use { $db }` command), or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
9146

9247
=== 08N03
9348

94-
Notifies the client that an exception occurred while trying to connect to a specified database.
49+
Status description:: error: connection exception - failed to write to graph. Failed to write to graph `$graph`. Check the defined access mode in both driver and database.
50+
51+
=== 08N04
52+
53+
Status description:: error: unable to route use clause. Routing with { $clause } is not supported in embedded sessions. Connect to the database directly or try running the query using a Neo4j driver or the HTTP API.
54+
55+
=== 08N05
56+
57+
Status description:: error: connection exception - unable to route administration command. Routing administration commands is not supported in embedded sessions. Connect to the system database directly or try running the query using a Neo4j driver or the HTTP API.
58+
59+
=== 08N06
60+
61+
Status description:: error: connection exception - protocol error. General network protocol error.
62+
63+
=== 08N07
64+
65+
Status description:: error: connection exception - not the leader. This member is not the leader.
66+
67+
//Possible solutions:
68+
//No write operations are allowed directly on this database. Connect to the leader directly or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
69+
70+
=== 08N08
71+
72+
Status description:: error: connection exception - database is read only. This database is read only on this server.
73+
74+
=== 08N09
75+
76+
Status description:: error: connection exception - database unavailable. The database { $db } is currently unavailable. Check the database status. Retry your request at a later time.
77+
78+
=== 08N10
79+
80+
Status description:: error: connection exception - invalid server state. The server is not in a state that can process a message of type: { $boltMsgType }.
81+
82+
=== 08N11
83+
84+
Status description:: error: connection exception - request error. The request is invalid and could not be processed by the server. See cause for further details.
85+
86+
=== 08N12
87+
88+
Status description:: error: connection exception - failed to parse bookmark. Failed to parse the supplied bookmark. Verify it is correct or check the debug log for more information.
89+
90+
=== 08N13
91+
92+
Status description:: error: connection exception - database not up to requested bookmark. The database { $db } is not up to the requested bookmark { $transactionId1 }. The latest transaction ID is { $transactionId2 }.
93+
94+
=== 08N14
9595

96-
.Error details
97-
[cols="<1s,<4"]
98-
|===
99-
|GQLSTATUS code
100-
m|08N03
101-
|Status description
102-
a|error: connection exception - failed to write to graph. Failed to write to graph `$graph`. Check the defined access mode in both driver and database.
103-
|Classification
104-
m|CLIENT_ERROR
105-
|===
96+
Status description:: error: connection exception - alias chains are not permitted. Unable to provide a routing table for the database identifed by the alias { $alias1 } because the request comes from another alias { $alias2 } and alias chains are not permitted.
10697

98+
=== 08N15
10799

100+
Status description:: error: connection exception - no such routing policy. Policy definition of the routing policy { $routingPolicy } could not be found. Verify that the spelling is correct.

0 commit comments

Comments
 (0)