1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
description: "connection-logging"
schemaVersion: "1.13"
runOnRequirements:
- topologies:
- single # The number of log messages is different for each topology since there is a connection pool per host.
createEntities:
- client:
id: &failPointClient failPointClient
tests:
- description: "Create a client, run a command, and close the client"
operations:
- name: createEntities
object: testRunner
arguments:
entities:
- client:
id: &client client
observeLogMessages:
connection: debug
- name: listDatabases
object: *client
arguments:
filter: {}
- name: close
object: *client
expectLogMessages:
- client: *client
messages:
- level: debug
component: connection
data:
message: "Connection pool created"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection pool ready"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection checkout started"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection created"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection ready"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
durationMS: { $$type: [double, int, long] }
- level: debug
component: connection
data:
message: "Connection checked out"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
durationMS: { $$type: [double, int, long] }
- level: debug
component: connection
data:
message: "Connection checked in"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
# The next three expected logs are for ending a session.
- level: debug
component: connection
data:
message: "Connection checkout started"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection checked out"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
durationMS: { $$type: [double, int, long] }
- level: debug
component: connection
data:
message: "Connection checked in"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection closed"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
reason: "Connection pool was closed"
- level: debug
component: connection
data:
message: "Connection pool closed"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
# This test exists to provide coverage of checkout failed and pool cleared events.
- description: "Connection checkout fails due to error establishing connection"
runOnRequirements:
- auth: true
minServerVersion: "4.0" # failCommand was added to mongod in 4.0
operations:
- name: createEntities
object: testRunner
arguments:
entities:
- client:
id: &client client
uriOptions:
retryReads: false
appname: &clientAppName clientAppName
# use a high heartbeatFrequencyMS to avoid a successful monitor check marking the pool as
# ready (and emitting another event) during the course of test execution.
heartbeatFrequencyMS: 10000
observeLogMessages:
connection: debug
- name: failPoint
object: testRunner
arguments:
client: *failPointClient
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["saslContinue"]
closeConnection: true
appName: *clientAppName
- name: listDatabases
object: *client
arguments:
filter: {}
expectError:
isClientError: true
expectLogMessages:
- client: *client
messages:
- level: debug
component: connection
data:
message: "Connection pool created"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection pool ready"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection checkout started"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection created"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection pool cleared"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
- level: debug
component: connection
data:
message: "Connection closed"
driverConnectionId: { $$type: [int, long] }
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
reason: "An error occurred while using the connection"
error: { $$exists: true }
unordered: true
- level: debug
component: connection
data:
message: "Connection checkout failed"
serverHost: { $$type: string }
serverPort: { $$type: [int, long] }
reason: "An error occurred while trying to establish a new connection"
error: { $$exists: true }
durationMS: { $$type: [double, int, long] }
unordered: true
|
