nodejs-pubsub: subscription.on message wasn't received of messagActually unrelated failures, but we should bump this anyway.es after 10 mins or more.

From @QTGate on September 7, 2017 17:42

  • OS: Debian
  • Node.js version: 8.4.0
  • npm version: 5.4.0
  • google-cloud-node version: 0.56.0
  • @google-cloud/pubsub version: 0.14.0

Steps to reproduce

const pubsub = require ( '@google-cloud/pubsub' )( connectOption )

const subscription = pubsub.topic ( topicName ).subscription ( subScription )

subscription.on ('message', message => {
    message.ack()
    ....
})

subscription.once('error', err => {
    ....
})

I received all un-received messages when I restart it. I checked the connectionPool object when it have not received message: connectionPool.isPaused [false] connectionPool.isOpen [true] connectionPool.connections [5]

Thank you.

Copied from original issue: GoogleCloudPlatform/google-cloud-node#2598

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 40 (30 by maintainers)

Most upvoted comments

So far, v 0.15.0 seems to be working 🤞

@stephenplusplus we are currently seeing this issue on Google App Engine with the latest release of the library, downgrading to 0.13.1 fixes the issue.

From what I can tell there are 4 issues being described here.

  1. Workers stop receiving messages until they are restarted (original issue) - Duplicate of #11
  2. Messages are being re-delivered - Duplicate of #2
  3. Possible memory leak - Duplicate of #13
  4. gRPC Stream Removed error - Duplicate of https://github.com/googleapis/nodejs-datastore/issues/35

Because there are already threads for the various issues being described here, I’m going to go ahead and close this issue. For inquiries about the status of one specific issue, please visit the corresponding thread mentioned above. For any other issues, please feel free to open a new issue if one does not already exist.

@stephenplusplus I’ll test this when I’m back at work on Tuesday and reply here