Keep receiving error when pushing to queue

[dennismonsewicz]

Here is the error I am getting:

Error: could send http://sqs.us-east-1.amazonaws.comundefined?MessageBody=%7B%22email%22%3A%22dennismonsewicz%40gmail.com%22%2C%22custom_activity_node_id%22%3A1%2C%22campaign_id%22%3A222%7D&Action=SendMessage...

I'm just not sure why this is error'ing out...

Here is how I am calling to it:

cfg = require '../../config/config'
sqs = require 'sqs'
log = console.log
queue = sqs(
  access: cfg.aws.access_key
  secret: cfg.aws.secret
  region: cfg.aws.region
)

router.post '/users/activities', (req, res, next) ->
  obj =
    user_id: req.body.user_id
    email: req.body.email if not req.body.user_id
    custom_activity_node_id: req.body.custom_activity_node_id
    campaign_id: req.body.campaign_id

  queue.push('user_activity', obj)

queue.pull 'user_activity', (data, callback)->
  log data
  callback()

[mafintosh]

lol the error message is missing a "not". i think this is failing because your region is undefined?

[mafintosh]

no its not the region after all. could you try upgrading to 0.3.0? it might produce a better error message.

[davidguttman]

Recently started seeing this a lot too. Upgraded to 1.3.0 but not providing much better info:

could not send http://sqs.us-east-1.amazonaws.com/176989213752/queue-name?ReceiptHandle=AQEBqJLqxiRurI0JkgqBDr7TSrh6khw%2BmTuSezVBsRHNfwB9iU5exWOw3%2B%2BtZkQ2F0YNVhLcoH%2FKCUCjpOMzyT99OMtIZKspvJMHRVXxxVol8ccDLKlguvG4Mq8fs0bhCLXxjExl9uGAoqgTxYhdo0ETHpnqONVDz14FGSoxr8i5LHJ99J4fmtQp8GwRbPo8CxebEMV6fmUnFQLAOCzni4%2FLvnR2qipmM2Fzo8jjVu7r7A7KJ1PyMJ8KC45soPqUYD1W2DWczopgYgMEtEt6YBZMKOpZmpNi4%2BzTj4hsC4gLDv5p7kGf5PZk14uQajHhk0Y1v9pSsse%2Fa4rCa6rBmlRTeA%3D%3D&Action=DeleteMessage&AWSAccessKeyId=ACCESSKEY&SignatureMethod=HmacSHA256&SignatureVersion=2&Expires=2015-07-14T22%3A07%3A31.341Z&Version=2012-11-05&Signature=iIfxbrjmAZVdfxgJyGaXeRhQYgivXm6hxbXBl2TdmUA%3D

[davidguttman]

We've noticed this issue happens a lot more frequently when there's a lot of CPU usage and the event loop gets blocked a bit. Not sure why that would cause an issue though.

[emkay]

I'm getting this when using pull, and it seems to only happen when there are a lot of items in the queue and workers is set to a high number. If I lower workers I'm not seeing this, even when I have 10k items in a queue.