Firebase Cloud Messaging(FCM) is basically used for application notification. Check the documentation below.
FCM messaging for HCL Verse for Android clients https://help.hcl-software.com/traveler/14.0.0/google_messaging.html
However, it seems you are running a old version of Domino and Traveler. You might want to consider upgrading to the latest versions.
HCL Traveler Fixes by Release https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0028394
Update: Starting on June 2, 2024 Extended Support will be available for Domino and Notes v9.0.x and v10.0.x https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0099055
Generally, These errors occur when the Traveler server attempts to push a notice to Google FCM servers but is unable to connect due to network issues (e.g., port restricted, URL blocked, or any other network limitation).
Also, Google has deprecated the legacy FCM APIs that Traveler 14.0.0.0 and prior was using for Android push notifications. Please refer below article for your better understanding.
Note: Support for Domino versions 9.0.x and 10.0.x ended in June 2024 and will not support the new Google FCM HTTP v1 API. Customers running older (unsupported) Domino versions will not have push notifications after installing Traveler 14.0.0 FP1. Background syncs will not be initiated; manual syncs will be required to get the latest data.
I would recommend to upgrade your Traveler server to v14.0.0 FP1.
Because Google has deprecated the legacy FCM APIs that Traveler was using for Android push notifications. Google has stared to intermittently rejecting FCM messages sent via the legacy API in July 2024 and could reject all such messages at any time; these rejections will be logged as errors by Traveler like "NTS_PUSH_FCM_RETRY_EXHAUSTED 0=3 1=https://fcm.googleapis.com/fcm/send Exception Thrown: java.io/IOException: Could not send message after 4 attempts".
Traveler will be supporting the Google FCM HTTP v1 API in Traveler v14.0.0 FP1.
For more information kindly check the link below:
Google FCM push notifications using legacy FCM APIs intermittently fail preventing background syncs in HCL Verse for Android
As you said, there are no sync issues; only getting these messages in the console, and these messages were not seen before yesterday.
In this case, the errors basically means Traveler server trying to push the notification to Google FCM servers and not being able to make a connection due to network issues. You may check with your N/W team to know if there are any recent changes in the network (e.g., port blocked, URL blocked, any other network restriction).
If you want to suppress these messages, you can use notes. ini "NTS_PUSH_ENABLE_FCM=false" to disable FCM connections.
Use the Domino console command "set config NTS_PUSH_ENABLE_FCM=false" to add it to the Traveler server notes.ini.
With the ini set, errors related to FCM should be stopped.
With 14.0 FP1 and the FCM api changes we found an issue where if you are using a Proxy for FCM and a firewall is in place (not allowing requests to Google) that the token renewal request is not going through the proxy and users will eventually hit a similar error with the same net result of push messages not working.
Please open a Case as we are working on a Hotfix to make sure all FCM requests go through the proxy. There is also have a workaround without opening the firewall that we can provide.
An immediate workaround would be to open the firewall on the Traveler server to Google FCM.
we have set these notifications to go through a proxy server. To make this work, we needed to add to notes.ini.
NTS_JAVA_PARMS_EXT=JAVA_PARMS_1 JAVA_PARMS_1=-Dhttps.proxyHost=proxy.company.com -Dhttps.proxyPort=3128 (for example, proxy host and port must be added according to your environment)
The "NTS_PUSH_FCM_RETRY_EXHAUSTED" error suggests a problem with Firebase Cloud Messaging (FCM), possibly due to an incorrect configuration or server redirect (HTTP 301). To resolve it, check your FCM setup, update the Traveler and Domino servers, and verify network settings. Make sure the correct ports are open for FCM. Consider reviewing logs for more details or contacting support. As an Engineering student, writing case studies isn’t my strong suit. I turned to https://academized.com/case-study-writing-service and their service was fantastic. The case study was comprehensive, logical, and written with a clear focus on the topic. It was formatted perfectly and included all the necessary diagrams and data. Their help allowed me to meet my deadline and improve my grades. I’m incredibly satisfied with their service!
