Callback parameters undefined in a callback running in Meteor

Question

I have a bit of code where I want to get the current message count from RabbitMQ from my Meteor App. Running the code in Node console gives the callback parameters correctly, but the same code in Meteor only gives the first parameter.

rabbitMQ = AMQP.createConnection({ host: '127.0.0.1' });

rabbitMQ.addListener('ready', function(){
  console.log('Connecting to the channel...');
});

rabbitMQ.addListener('ready', function(){

   rabbitMQ.queue('foo', {durable:true, autoDelete:false}, function (queue, messages, consumers) {
     console.log('Queue ' + queue.name + ' is open with ' + messages + ' messages');
   });

});

In Node Prints:

Connecting to the channel...
Queue foo is open with 3 messages

In Meteor Prints:

Connecting to the channel...
Queue foo is open with undefined messages

Any ideas on why only the first (queue) parameter comes through when running in Meteor? I'm a Meteor noob, so maybe it's a Fibers issue?

I recommend you sir to paste your Meteor code so others can help — gabrielhpugliese, Jul 13 '13 at 17:24

score 0 · Answer 1 · answered Aug 07 '13 at 19:49

0

I decided that keeping track in Mongo with state changes was easier than debugging this problem.

answered Aug 07 '13 at 19:49

DataRiot

476
3
8

Callback parameters undefined in a callback running in Meteor

1 Answers1