Bad credentials file causes Pub/Sub topic creation to hang
See original GitHub issueSee: https://github.com/spring-cloud/spring-cloud-gcp/issues/962. I suspect that the root cause is in the client library.
Note that when the same credentials file is used to publish a message to a topic, an appropriate exception is thrown saying java.io.IOException: Error getting access token for service account
and 401 Unauthorized
.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Bad credentials file causes Pub/Sub topic creation to hang #962
Steps to reproduce: Create and download a GCP service account key (JSON file). Make sure the key is actually deleted in the Cloud...
Read more >Troubleshooting | Cloud Pub/Sub Documentation
Publish operations fail with DEADLINE_EXCEEDED. This is likely caused by a client side bottleneck, such as insufficient service CPUs, bad thread health, or ......
Read more >Error in trying to create a topic subscription in Google PubSub ...
I found the issue. I re-ran gcloud auth application-default login. and made sure that GOOGLE_APPLICATION_CREDENTIALS was pointed to the new ...
Read more >Troubleshooting AWS IoT Greengrass V2
Use the troubleshooting information and solutions in this section to help resolve issues with AWS IoT Greengrass Version 2. Topics. View AWS IoT...
Read more >Spring Framework on Google Cloud
Publish and subscribe to Google Cloud Pub/Sub topics ... The project ID specified in the JSON credentials file pointed by the GOOGLE_APPLICATION_CREDENTIALS ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This repeats over and over in the logs when running an Integration test after the key has been deleted:
Earlier in the year I filed an issue to see if we can fix this problem: https://github.com/grpc/grpc-java/issues/6808
From what it looks like I don’t think the problem will be fixed due to certain technical reasons… I think we’ll just have to live with the 10-minute timeout.
Returning this to closed.