-
Notifications
You must be signed in to change notification settings - Fork 696
PubsubInboundChannelAdapter swallows error when connected to non-existent subscription #82
Comments
The Would be better to use |
Another (more expensive, but more explicit) alternative is to make an explicit check for the existence of the Subscription using the This behaviour should be parameterised. |
@artembilan logging sounds good, however, that still doesn't solve the need from the client code to have an explicit way to inspect/handle subscription errors and have the option to fail/retry/ignore. I guess we could combine the two suggested behaviors: we listen on the lifecycle events and "on failure" we can inspect if the error is due to missing subscription ("NOT_FOUND: Resource not found (resource=[subscription])." and if that's the case we can have a configurable behavior + a status accessible from the client side probably via a status listener? |
Well, in other places we expose the |
This was apparently fixed in a recent version of the google-cloud-pubsub library, as I'm now seeing errors logged when trying to subscribe to a non-existing subscription. |
* Pivotal --> Google in pom files, capitalize GCP
Currently if I connect a PubsubInboundChannelAdapter to a non-existent subscription, it silently fails.
We could change this behaviour by changing this line:
We could add an
.awaitRunning()
to ensure that when the subscriber started that it is actually running.The text was updated successfully, but these errors were encountered: