This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


May 9, 2018, 4:31 AM
12 Posts
topic has been resolvedResolved

Traveler

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: traveler,traveler android,google cloud messaging,firebase cloud messaging
  • Replies: 1

Hello All

I have a unique question about Traveler. Up until this morning, the mobile admin asked me about the following error:

[1BAC:0229-1D28] 09/05/2018 10:35:05   Traveler: SEVERE  xxxxx There was an issue sending the notification message to the Google Cloud Messaging (GCM) server. 3 attempts to re-establish the connection have failed, so thessage cannot be sent. You can test network connectivity including firewall settings by trying https://android.googleapis.com/gcm/send in a web browser on this server. Exception Thrown: java.net.ConnectException: Connection timed out: connect 

So he got on the hotline with the netwrok team and they granted the traffic outbound. All fine and dandy. Yet if you click on this link https://android.googleapis.com/gcm/send  the google page has a disclaimer that GCM is moving Firebase Cloud Messaging (FCM) (The GCM server and client APIs are deprecated and will be removed as soon as April 11, 2019).

Has anyone experienced this before?

Has anyone perhaps contacted IBM and asked if Traveler going forward with make allowance for this?

Or, is there a way to fix this somehow?

Any thoughts or ideas would be welcomed. And if there is a way to get this relevant information to the IBM Traveler think-tank, let me know.

 

Thanks in advance

Jason

Jun 7, 2018, 1:00 AM
12 Posts
Resolved

So, I had a long look at this error on the Traveler console.

I asked the network team/s to create a rule to allow the traffic outbound. When that rule was applied the errors went away.

This was due to a user not receiving realtime updates on its device. After the rule change, they could.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal