firebase / firebase/firebase-admin-java

Firebase Messaging throws exception and doesn't get back until server restart

オープン
#794 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る
api: messaging needs-triage
主要言語
Java
スター
620
フォーク
305
平均マージ
3時間 23分
マージ済み PR(30日)
1

説明

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?

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
java
領域
api, authentication, backend
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
25/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。