Java – GCM – failed to publish JSON request to GCM after 6 attempts
I have the same problem as this I will try to provide more information
I'm using the play framework, written in Java I wrote a plug - in called pushnotificationqueue Pushnotificationqueue runs IOS and Android push message queues at the same time The following is my GCM implementation reference
public class AndroidPushNotificationQueue {
// (constructors and fields not included for brevity)
// constructor starts a daemon thread
/**
* Sends a notification.
* @param notifyKeys - device tokens
* @param data - data to send
**/
public void sendNotification(List<String> notifyKeys,Map<String,String> data) {
if (notifyKeys.size() == 0) {
return;
}
Builder b = new Message.Builder();
if (data != null) {
for (String key : data.keySet()) {
b.addData(key,data.get(key));
}
}
if (testMode) {
b.dryRun(true);
}
Message message = b.build();
queue.add(new Notification(notifyKeys,message));
}
public void stop() {
stopped = true;
sendingThread.interrupt();
}
private class SendNotificationRunner implements Runnable {
@Override
public void run() {
while (true) {
try {
sendNotifications();
//TODO: handle errors
} catch (InterruptedException e) {
if (stopped) break;
Logger.error("Error processing android notification",e);
} catch (InvalidRequestException e) {
if (stopped) break;
Logger.error("Error processing android notification",e);
} catch (IOException e) {
if (stopped) break;
Logger.error("Error processing android notification",e);
} catch (Exception e) {
if (stopped) break;
Logger.error("Unexpected Exception in Android Notification thread",e);
}
}
Logger.info("Stopping Android push queue");
}
private void sendNotifications() throws IOException,InterruptedException,InvalidRequestException {
Notification n = queue.take(); // will wait until an element becomes available
MulticastResult result = sender.send(n.message,n.notifyKeys,NUM_RETRIES);
List<Result> results = result.getResults();
for (int i = 0; i < results.size(); ++i) {
Result r = results.get(i);
String mId = r.getMessageId();
String notifyKey = n.notifyKeys.get(i);
if (mId == null) {
String error = r.getErrorCodeName();
if (error.equals(Constants.ERROR_NOT_REGISTERED)) {
removeDeadRegistration(notifyKey);
} else {
//TODO: something better when error occurs
Logger.error("Error sending android notification to " + notifyKey + ": " + error);
}
} else {
String newNotifyKey = r.getCanonicalRegistrationId();
if (newNotifyKey != null && !newNotifyKey.equals(notifyKey)) {
// do something to handle this error case - not included for brevity
}
}
}
}
}
This works... Sometimes Most of the time I get the following errors
java.io.IOException: Could not post JSON requests to GCM after 6 attempts at com.google.android.gcm.server.Sender.send(Sender.java:319) ~[classes/:na] at utils.AndroidPushNotificationQueue$SendNotificationRunner.sendNotifications(AndroidPushNotificationQueue.java:131) ~[classes/:na] at utils.AndroidPushNotificationQueue$SendNotificationRunner.run(AndroidPushNotificationQueue.java:103) ~[classes/:na] at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55] [debug] application - Endpoint - BaseStationAuth.getUsername
I did some digging and found this in the GCM implementation
/**
* Sends a message to one device,retrying in case of unavailability.
*
* <p>
* <strong>Note: </strong> this method uses exponential back-off to retry in
* case of service unavailability and hence Could block the calling thread
* for many seconds.
*
* @param message message to be sent,including the device's registration id.
* @param registrationId device where the message will be sent.
* @param retries number of retries in case of service unavailability errors.
*
* @return result of the request (see its javadoc for more details).
*
* @throws IllegalArgumentException if registrationId is {@literal null}.
* @throws InvalidRequestException if GCM didn't returned a 200 or 5xx status.
* @throws IOException if message Could not be sent.
*/
public Result send(Message message,String registrationId,int retries)
throws IOException {
int attempt = 0;
Result result = null;
int backoff = BACKOFF_INITIAL_DELAY;
boolean tryAgain;
do {
attempt++;
if (logger.isLoggable(Level.FINE)) {
logger.fine("Attempt #" + attempt + " to send message " +
message + " to regIds " + registrationId);
}
result = sendNoRetry(message,registrationId);
tryAgain = result == null && attempt <= retries;
if (tryAgain) {
int sleepTime = backoff / 2 + random.nextInt(backoff);
sleep(sleepTime);
if (2 * backoff < MAX_BACKOFF_DELAY) {
backoff *= 2;
}
}
} while (tryAgain);
if (result == null) {
throw new IOException("Could not send message after " + attempt +
" attempts");
}
return result;
}
I changed the number of attempts – 5, 10, 15
>Has anyone else encountered this problem? I found some people with the same problem on the Internet, but so far I haven't found a solution. > Any suggestions I can try to solve? > Should I continue to increase the number of attempts?
Solution
I have the same problem But solve it
1. I just want to edit 'sender' BACKOFF_ INITIAL_ DELAY = 1000;’ To 'sender BACKOFF_ INITIAL_ DELAY = 10000;’ Interval variable On COM google. android. gcm. Sender on server Java
You can read sender Java file It is open source
2. I will collaps_ Change the key value to the long type in the GCM payload I don't think Google servers accept collaps_ Special characters of key “.”, ",", any alphabet
Good luck
