On Thu, Apr 24, 2014 at 11:51 AM, Florian Schrofner <florian.schrofner@outlook.com> wrote:
No, I don't mind at all..

Should I just set up a new UPS cartridge and test if the server crashes
again, or should I check for the keystore?

yeah, just spin up a new instance, via the OpenShift UI (using our cartridge there)
 

By the way there really seem to be some problems concerning Google Cloud
Messaging itself.. I didn't receive any other push notifications today
(except from an Asian messenger my girlfriend made me use,

:-)
 
I assume it
doesn't use GCM in order to address the Chinese market). Suddenly all
notifications (including the aerogear notifications) arrived and my phone
started going nuts.

So maybe it isn't your fault after all..

Also I don't think it's only my phone, because my colleague also didn't
receive any aerogear notifications the day before yesterday (although he had
no problems with it today) until I restarted the server.
Maybe GCM made the UPS server crash, because it had some problems/unexpected
behaviour?

I have added a JIRA to be a bit more lenient:
https://issues.jboss.org/browse/AGPUSH-624

 



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Problems-sending-notifications-Cordova-tp7515p7566.html
Sent from the aerogear-dev mailing list archive at Nabble.com.
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf