You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2018. It is now read-only.
The interrupt handler tries to call bench.monitor.isRunning() which isn't defined anywhere:
websocket-bench -t faye -a 3500 -c 50 ws://localhost:3100/faye
Launch bench with 3500 total connection, 50 concurent connection
0 message(s) send by client
1 worker(s)
WS server : faye
^C
Gracefully stoping worker from SIGINT (Ctrl+C)
/usr/local/lib/node_modules/websocket-bench/index.js:102
if (bench.monitor.isRunning()) {
^
TypeError: undefined is not a function
at null._onTimeout (/usr/local/lib/node_modules/websocket-bench/index.js:102:23)
at Timer.listOnTimeout (timers.js:119:15)
The text was updated successfully, but these errors were encountered:
Gracefully stoping worker from SIGINT (Ctrl+C)
/usr/lib/node_modules/websocket-bench/index.js:102
if (bench.monitor.isRunning()) {
^
TypeError: bench.monitor.isRunning is not a function
at null._onTimeout (/usr/lib/node_modules/websocket-bench/index.js:102:23)
at Timer.listOnTimeout (timers.js:92:15)
The interrupt handler tries to call
bench.monitor.isRunning()
which isn't defined anywhere:The text was updated successfully, but these errors were encountered: