New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spring Cloud GCP Pub/Sub reconnection : Subscriber doesn't receive message after subscription is delete and recreated with same name for same topic #2606
Comments
When I replicate the above steps, I am able to receive the message from the recreated subscription; however, when the client attempts to ACK, I get the following exceptions:
and
Found the following thread that discusses this behavior: https://groups.google.com/g/cloud-pubsub-discuss/c/seAgY28sVc0
So this does not appear to be a use case that is supported. |
ok. any plan to support in the near future? I get the below exception as soon as subscription is deleted. ` com.google.api.gax.rpc.NotFoundException: com.google.api.gax.rpc.NotFoundException: io.grpc.StatusRuntimeException: NOT_FOUND: Resource not found (resource=projects/project1/subscriptions/test-sub). 2024-02-15T21:46:59.410+05:30 WARN 73572 --- [test-app] [Subscriber-SE-1-3] c.g.c.p.v.StreamingSubscriberConnection : Setting response: SUCCESSFUL on outstanding messages |
Given the linked thread is from 2017, this seems like very established behavior which is unlikely to be modified near-term. @maitrimangal, could you verify? @Vaageesh, consider submitting a support ticket @ https://cloud.google.com/support/. This will ensure your situation gets attention and may result in guidance on how to achieve your end goal. |
Closing this ticket, as it is not Spring Cloud GCP specific. Please submit a ticket to https://cloud.google.com/support/ if this use case is something you wish the service to consider changing. |
Describe the bug
Sample
Expected that pubSub client must reconnect to same subscription after few mins.
I am wondering if any configuration available for this?
The text was updated successfully, but these errors were encountered: