hazelcast / hazelcast/hazelcast-nodejs-client

ERROR at HazelcastClient: Client failed to start [API-1806]

Open
#1,449 1 comment 0 reactions 0 assignees View on GitHub
Source: Internal to-jira Type: Defect
Dominant language
TypeScript
Stars
152
Forks
64
Avg merge
46m
Merged PRs (30d)
3

Description

Nightly tests on master failed.
Error:
[DefaultLogger] ERROR at HazelcastClient: Client failed to start.
IllegalStateError: Unable to connect to any cluster.
at new IllegalStateError (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\src\core\HazelcastError.ts:143:9)
at D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\src\network\ConnectionManager.ts:444:23
at async TestFactory._createClient (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\test\TestUtil.js:530:24)
at async TestFactory.newHazelcastClientForParallelTests (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\test\TestUtil.js:526:16)
at async Context. (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\test\integration\backward_compatible\parallel\ssl\ClientSSLAuthenticationTest.js:160:17) {
cause: undefined,
serverStackTrace: undefined
}

Stdout:
=====
[DefaultLogger] INFO at LifecycleService: HazelcastClient is SHUTTING_DOWN
[DefaultLogger] ERROR at HazelcastClient: Client failed to start.
IllegalStateError: Unable to connect to any cluster.
at new IllegalStateError (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\src\core\HazelcastError.ts:143:9)
at D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\src\network\ConnectionManager.ts:444:23
at async TestFactory._createClient (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\test\TestUtil.js:530:24)
at async TestFactory.newHazelcastClientForParallelTests (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\test\TestUtil.js:526:16)
at async Context. (D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\test\integration\backward_compatible\parallel\ssl\ClientSSLAuthenticationTest.js:160:17) {
cause: undefined,
serverStackTrace: undefined
}
[DefaultLogger] INFO at LifecycleService: HazelcastClient is SHUTDOWN
[DefaultLogger] INFO at LifecycleService: HazelcastClient is STARTING
[DefaultLogger] INFO at LifecycleService: HazelcastClient is STARTED
[DefaultLogger] INFO at ConnectionManager: Trying to connect to 127.0.0.1:55761
[DefaultLogger] WARN at ConnectionManager: Error during initial connection to 127.0.0.1:55761 Error: self-signed certificate
[DefaultLogger] WARN at WaitStrategy: Unable to get live cluster connection, retry in 973 ms, attempt: 1, cluster connect timeout: 1000 ms, max backoff millis: 30000
[DefaultLogger] INFO at ConnectionManager: Trying to connect to 127.0.0.1:55761
[DefaultLogger] WARN at ConnectionManager: Error during initial connection to 127.0.0.1:55761 Error: self-signed certificate
[DefaultLogger] WARN at WaitStrategy: Unable to get live cluster connection, cluster connect timeout (1000 ms) is reached. Attempt 2
at processTimers (node:internal/timers:507:7)
Caused by Error: No connection found to cluster.
at new IOError (src\core\HazelcastError.ts:167:9)
at ConnectionRegistryImpl.checkIfInvocationAllowed (src\network\ConnectionRegistry.ts:188:21)
at InvocationService.invokeSmart (src\invocation\InvocationService.ts:543:51)
at listOnTimeout (node:internal/timers:564:17)
at processTimers (node:internal/timers:507:7)

2) MultiMapProxyLockTest
"after each" hook for "gives up attempt to lock after timeout is exceeded":
Error: Invocation 16) reached its deadline.
at new OperationTimeoutError (src\core\HazelcastError.ts:173:9)
at InvocationService.rejectIfNotRetryable (src\invocation\InvocationService.ts:683:40)
at InvocationService.notifyError (src\invocation\InvocationService.ts:649:18)
at InvocationService.invokeSmart (src\invocation\InvocationService.ts:545:22)
at listOnTimeout (node:internal/timers:564:17)
at processTimers (node:internal/timers:507:7)
Caused by Error: No connection found to cluster.
at new IOError (src\core\HazelcastError.ts:167:9)
at ConnectionRegistryImpl.checkIfInvocationAllowed (src\network\ConnectionRegistry.ts:188:21)
at InvocationService.invokeSmart (src\invocation\InvocationService.ts:543:51)
at listOnTimeout (node:internal/timers:564:17)
at processTimers (node:internal/timers:507:7)

3) Uncaught error outside test suite:
Uncaught Workerpool Worker terminated Unexpectedly
exitCode: `134`
signalCode: `null`
workerpool.script: `D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\node_modules\mocha\lib\nodejs\worker.js`
spawnArgs: `C:\hostedtoolcache\windows\node\18.12.1\x64\node.exe,D:\a\hazelcast-nodejs-client\hazelcast-nodejs-client\node_modules\mocha\lib\nodejs\worker.js`
spawnfile: `C:\hostedtoolcache\windows\node\18.12.1\x64\node.exe`
stdout: `null`
stderr: `null`

Error: Workerpool Worker terminated Unexpectedly
exitCode: `134`
signalCode: `null`
spawnfile: `C:\hostedtoolcache\windows\node\18.12.1\x64\node.exe`
stdout: `null`
stderr: `null`

at ChildProcess. (node_modules\workerpool\src\WorkerHandler.js:294:13)
at ChildProcess.emit (node:events:513:28)
at ChildProcess.emit (node:domain:489:12)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)

Stopping cluster and remote controller
Error: Process completed with exit code 1.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.