Firebase Messaging throws exception and doesn't get back until server restart
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- api, authentication, backend
Research direction
Start with the pom.xml dependency on firebase-admin 9.1.1 and trace the FirebaseMessagingException path for service-account access-token failures. Gather logs around the intermittent failure and compare behavior before and after a WildFly restart; done means identifying a reproducible cause and documenting a reliable fix or confirming an SDK issue.
Written by the indexing model from the issue text.
Description
I have a system built with spring boot, java 8 and hosted on google cloud using compute engine.
My server app is wildfly 21.0.1.Final.
I am using firebase messaging 9.1.1 to deliver notifications to the application users.
The service is working fine most of the time, however, I get this error from time to time.
com.google.firebase.messaging.FirebaseMessagingException: Failed to establish a connection: Error getting access token for service account: IP_OF_PROXY_HOST_GOES_HERE, iss: firebase-adminsdk-project@projectname.iam.gserviceaccount.com
As a workaround, I do a full server (wildfly) restart to get the service back.
In my pom file, I have:
com.google.firebase
firebase-admin
9.1.1
I have searched for similar issues and checked:
1- The system clock is synchronized
2- Firewall access to firebase
3- The service works well and the issue happens randomly from time to time.
4- I can not reproduce since I don't know the cause.
Note: I don't use any other firebase service in this product.
Does anyone know what is happening and how to overcome this issue?
- Dominant language
- Java
- Stars
- 620
- Forks
- 305
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/firebase-admin-java
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
firebase/firebase-admin-java#1231 ·
-
api: core
firebase/firebase-admin-java#1198 · 3 comments · 1 assignee ·
-
api: remoteconfig
firebase/firebase-admin-java#1196 · 1 comment · 2 assignees ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
firebase/firebase-admin-java#1192 · 3 comments ·
-
needs-triage type: feature request
Difficulty 3/5 1-2 days Newbie friendliness 45/100
firebase/firebase-admin-java#1149 · 1 comment ·
All issues in firebase/firebase-admin-java
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cryptomator/hub#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
johanhaleby/occurrent#1120 ·