warning: possible EventEmitter memory leak detected.

[pepijndevos]

When trying to connect to a remote RabbitMQ, no data is received and it shows 2 of these warnings. Any idea what's wrong?

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at Connection.EventEmitter.addListener (events.js:160:15)
    at Connection.connect (/usr/lib/node_modules/amqp-tool/node_modules/amqp-dsl/node_modules/amqp/amqp.js:1068:8)
    at Connection.reconnect (/usr/lib/node_modules/amqp-tool/node_modules/amqp-dsl/node_modules/amqp/amqp.js:1038:8)
    at null._onTimeout (/usr/lib/node_modules/amqp-tool/node_modules/amqp-dsl/node_modules/amqp/amqp.js:876:16)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

This is the command I'm using

 amqp-tool --host blabla.bigwig.lshift.net --port 10035 --user foo --password password --queue celery --exchange celery --count 5000 --export dump.json

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4400402-warning-possible-eventemitter-memory-leak-detected?utm_campaign=plugin&utm_content=tracker%2F2158434&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2158434&utm_medium=issues&utm_source=github).

[pepijndevos]

I was missing the --vhost, but the warning could possibly be fixed =)

[FGRibreau]

@pepijndevos I am sorry I don't have the time to fix it right now, could you send a pull request ?

was this problem ever fixed?

[FGRibreau]

@amitmiran I am not sure. If not you can always send a pull-request to fix it, in either case it's not a big issue regarding amqp-tool general usage.