From dariusz.skrzypon at infakt.pl Mon Jan 9 03:53:44 2017 From: dariusz.skrzypon at infakt.pl (=?utf-8?Q?Dariusz_Skrzypo=C5=84?=) Date: Mon, 9 Jan 2017 09:53:44 +0100 Subject: [Aerogear-users] Openshift memory and deployment problems Message-ID: <3A77A8FD-5631-48D5-BB51-F1B834D03622@infakt.pl> Hello, We?ve been using aerogear-unified-push on openshift large gear for some time. We have two problems, which I cannot find any answers for. I?m in no way experienced on this field 1) Application goes offline once in a while - it appears it uses whole instance?s memory after some time, causing OutOfMemory error. This happens once every 1-2 weeks for us. So, I figured - let?s workaround these memory problems by restarting the app once a while, however: 2) Restarting application doest work. After I run restart from openshift console - cartridge appears to be restarted, wildfly is running, however browsing to /ag-push results in 404 Not Found. I need to manually use rhc-port-forward, then go to wildfly admin console and redeploy artifacts by uploading/enabling them. 3) This might be related to ?control restart? output: [xxx.rhcloud.com bin]\> ./control restart Restarting aerogear-push cart Stopping aerogear-push cart Sending SIGTERM to wildfly:462504 ... Starting aerogear-push cart Found 127.10.62.129:8080 listening port Found 127.10.62.129:9990 listening port /var/lib/openshift/xxx/aerogear-push/standalone/deployments /var/lib/openshift/xxx/aerogear-push/bin /var/lib/openshift/xxx/aerogear-push/bin CLIENT_MESSAGE: Artifacts in an unknown state: ./auth-server.war ./ag-push.war Two war files in deployments folder are present, however they are in .undeployed status. Snapshots are not working for us either. The most important thing for us now, is to provide automatic means of restarting the cartridge, which would result in usable application. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170109/271a9418/attachment-0001.html From benjamin.fras at petafuel.de Tue Jan 10 05:18:38 2017 From: benjamin.fras at petafuel.de (benjaminfras) Date: Tue, 10 Jan 2017 03:18:38 -0700 (MST) Subject: [Aerogear-users] Many established connections to Apple servers Message-ID: <1484043518460-1004.post@n5.nabble.com> Hi, we have an aerogear installation deployed on a EAP 6.4.11 domain mode. It is working fine so far, however after some time we see plenty of open connections to apple servers (17.188). Today we hit a peak with over 3000 open connections. It seems that each connection is tied to a separate thread, thus we had over 3000 threads as well. This is when our monitoring fired and our operation guy got alerted. On average we're sending approx. 40 push messages every 5 minutes to both android and ios devices. This is a snippet of what the netstat output looks like: Is this expected behavior? Is it possible to set a max limit or something similar? -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Many-established-connections-to-Apple-servers-tp1004.html Sent from the aerogear-users mailing list archive at Nabble.com. From a.r.dabrowski at gmail.com Wed Jan 11 05:15:15 2017 From: a.r.dabrowski at gmail.com (r00dY) Date: Wed, 11 Jan 2017 03:15:15 -0700 (MST) Subject: [Aerogear-users] Android SDK doesn't work, any way to debug? Message-ID: <1484129715269-1007.post@n5.nabble.com> Hi guys, I've implemented aerogear push in Titanium app, iOS native app, so far so good. Now need to integrate AG into Android and I'm struggling. Steps I've done: 1. Set up project and app in Firebase console. 2. (tested push notifications by native Firebase SDK - they worked). 3. I add to gradle following stuff: compile 'com.google.firebase:firebase-messaging:9.8.0' compile 'org.jboss.aerogear:aerogear-android-push:4.1.0' and use google-services plugin, version 3 4. I create Aerogear Android variant, set up Google API key (tried legacy and new) and project ID from Firebase console (the ones that worked in a native way). 5. I register for pushes using AG SDK and registration is OK (see new device in admin panel). 6. I set up DEFAULT_MESSAGE_HANDLER_KEY variable. 7. I create message handler. 8. I send test push via "Send notification to this app" form. I set up text, the rest of fields is left to "All". 9. I get callback that push notification is successfully sent. 10. Nothing happens on my device (tried Android 5, 6 and 7). I was quite frustrated so I downloaded example project HelloPush https://github.com/aerogear/aerogear-android-cookbook/tree/master/HelloPush, created for it new app in Firebase console and set up all configuration data from my AeroGear panel. Same thing happens. Any idea what may be the reason or do you have any methods for more detailed debugging like: 1. Debugging of internals in Aerogear SDK, some verbose logging etc. 2. Debugging what's going on between Aerogear and Firebase while sending push? Because I'm not sure if it's SDK fault or a fault of communication between Aerogear and Firebase. I can't wait for your answers, best! -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-SDK-doesn-t-work-any-way-to-debug-tp1007.html Sent from the aerogear-users mailing list archive at Nabble.com. From cristian.morariu at gmail.com Thu Jan 12 04:13:09 2017 From: cristian.morariu at gmail.com (crysm) Date: Thu, 12 Jan 2017 02:13:09 -0700 (MST) Subject: [Aerogear-users] Multiple aliases with the same token Message-ID: <1484212389700-1008.post@n5.nabble.com> Hi, is it possible to register several aliases with the same token? If not, are there any plans for this feature? Regards, Cristian -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Multiple-aliases-with-the-same-token-tp1008.html Sent from the aerogear-users mailing list archive at Nabble.com. From cristian.morariu at gmail.com Thu Jan 12 04:13:56 2017 From: cristian.morariu at gmail.com (crysm) Date: Thu, 12 Jan 2017 02:13:56 -0700 (MST) Subject: [Aerogear-users] Multiple aliases with the same token In-Reply-To: <1484212389700-1008.post@n5.nabble.com> References: <1484212389700-1008.post@n5.nabble.com> Message-ID: <1484212436183-1009.post@n5.nabble.com> I was referring to the Unified Push Server. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Multiple-aliases-with-the-same-token-tp1008p1009.html Sent from the aerogear-users mailing list archive at Nabble.com. From matzew at apache.org Wed Jan 18 15:53:57 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Jan 2017 21:53:57 +0100 Subject: [Aerogear-users] Multiple aliases with the same token In-Reply-To: <1484212436183-1009.post@n5.nabble.com> References: <1484212389700-1008.post@n5.nabble.com> <1484212436183-1009.post@n5.nabble.com> Message-ID: not planed, we have categories, you can have multiple categories per device On Thu, Jan 12, 2017 at 10:13 AM, crysm wrote: > I was referring to the Unified Push Server. > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Multiple-aliases-with-the-same-token-tp1008p1009.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/0f2a6443/attachment.html From matzew at apache.org Wed Jan 18 15:57:28 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Jan 2017 21:57:28 +0100 Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: <1484043518460-1004.post@n5.nabble.com> References: <1484043518460-1004.post@n5.nabble.com> Message-ID: only apple? they should be cleaned up... FWIW, we are looking at replacing their existing APIs w/ their newer HTTP/2 backend... but that's not yet started, but on the pipeline On Tue, Jan 10, 2017 at 11:18 AM, benjaminfras wrote: > Hi, > we have an aerogear installation deployed on a EAP 6.4.11 domain mode. It > is > working fine so far, however after some time we see plenty of open > connections to apple servers (17.188). Today we hit a peak with over 3000 > open connections. It seems that each connection is tied to a separate > thread, thus we had over 3000 threads as well. This is when our monitoring > fired and our operation guy got alerted. > On average we're sending approx. 40 push messages every 5 minutes to both > android and ios devices. > > This is a snippet of what the netstat output looks like: > > > Is this expected behavior? Is it possible to set a max limit or something > similar? > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Many-established-connections-to-Apple-servers-tp1004.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/6ea818fc/attachment.html From matzew at apache.org Wed Jan 18 15:58:17 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 18 Jan 2017 21:58:17 +0100 Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: References: <1484043518460-1004.post@n5.nabble.com> Message-ID: btw. I did not see the snippet - mind providing it via gist ? thx On Wed, Jan 18, 2017 at 9:57 PM, Matthias Wessendorf wrote: > only apple? > > they should be cleaned up... > > FWIW, we are looking at replacing their existing APIs w/ their newer > HTTP/2 backend... but that's not yet started, but on the pipeline > > On Tue, Jan 10, 2017 at 11:18 AM, benjaminfras > wrote: > >> Hi, >> we have an aerogear installation deployed on a EAP 6.4.11 domain mode. It >> is >> working fine so far, however after some time we see plenty of open >> connections to apple servers (17.188). Today we hit a peak with over 3000 >> open connections. It seems that each connection is tied to a separate >> thread, thus we had over 3000 threads as well. This is when our monitoring >> fired and our operation guy got alerted. >> On average we're sending approx. 40 push messages every 5 minutes to both >> android and ios devices. >> >> This is a snippet of what the netstat output looks like: >> >> >> Is this expected behavior? Is it possible to set a max limit or something >> similar? >> >> >> >> -- >> View this message in context: http://aerogear-users.1116366. >> n5.nabble.com/Many-established-connections-to-Apple-servers-tp1004.html >> Sent from the aerogear-users mailing list archive at Nabble.com. >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/471a8def/attachment-0001.html From columfoskin at gmail.com Wed Jan 18 16:08:54 2017 From: columfoskin at gmail.com (columfoskin) Date: Wed, 18 Jan 2017 14:08:54 -0700 (MST) Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue Message-ID: <1484773734164-1013.post@n5.nabble.com> Hey all, I am working on building a Node js version of the backend for the Aerodoc application and have some questions if anyone can help it would be great. Can anybody help me to understand when the lat/long pairs are sent from the android device to the Aerodoc backend? I have spent some time debugging and trying to figure this out - without much success. I have been looking at the request sent from the android app on login and it is not then. My guess from looking at the Java code is this happens when when a HTTP PUT is called on the ?saleagents? endpoint but I cannot determine when that endpoint is hit (from looking at the code & debugging). Also, from what I see, updates to the agents status are sending a POST to the backend, and not a PUT and therefore hitting my POST endpoint - causing issues. Is this expected behaviour? Any insight or help appreciated. Colum. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating-agent-status-issue-tp1013.html Sent from the aerogear-users mailing list archive at Nabble.com. From dpassos at redhat.com Wed Jan 18 16:15:45 2017 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 18 Jan 2017 19:15:45 -0200 Subject: [Aerogear-users] Android SDK doesn't work, any way to debug? In-Reply-To: <1484129715269-1007.post@n5.nabble.com> References: <1484129715269-1007.post@n5.nabble.com> Message-ID: Hi What version of UPS are you using? On Wed, Jan 11, 2017 at 8:15 AM, r00dY wrote: > Hi guys, > > I've implemented aerogear push in Titanium app, iOS native app, so far so > good. Now need to integrate AG into Android and I'm struggling. > > Steps I've done: > 1. Set up project and app in Firebase console. > 2. (tested push notifications by native Firebase SDK - they worked). > 3. I add to gradle following stuff: > > compile 'com.google.firebase:firebase-messaging:9.8.0' > compile 'org.jboss.aerogear:aerogear-android-push:4.1.0' > > and use google-services plugin, version 3 > > 4. I create Aerogear Android variant, set up Google API key (tried legacy > and new) and project ID from Firebase console (the ones that worked in a > native way). > 5. I register for pushes using AG SDK and registration is OK (see new > device > in admin panel). > 6. I set up DEFAULT_MESSAGE_HANDLER_KEY variable. > 7. I create message handler. > 8. I send test push via "Send notification to this app" form. I set up > text, > the rest of fields is left to "All". > 9. I get callback that push notification is successfully sent. > 10. Nothing happens on my device (tried Android 5, 6 and 7). > > I was quite frustrated so I downloaded example project HelloPush > https://github.com/aerogear/aerogear-android-cookbook/ > tree/master/HelloPush, > created for it new app in Firebase console and set up all configuration > data > from my AeroGear panel. Same thing happens. > > Any idea what may be the reason or do you have any methods for more > detailed > debugging like: > 1. Debugging of internals in Aerogear SDK, some verbose logging etc. > 2. Debugging what's going on between Aerogear and Firebase while sending > push? Because I'm not sure if it's SDK fault or a fault of communication > between Aerogear and Firebase. > > I can't wait for your answers, best! > > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Android-SDK-doesn-t-work-any-way-to-debug-tp1007.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/579f5a32/attachment.html From dpassos at redhat.com Wed Jan 18 16:22:55 2017 From: dpassos at redhat.com (Daniel Passos) Date: Wed, 18 Jan 2017 19:22:55 -0200 Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: <1484773734164-1013.post@n5.nabble.com> References: <1484773734164-1013.post@n5.nabble.com> Message-ID: Hi, This features was removed[1] by me. For more details here[2] is where magic happened [1] https://github.com/aerogear/aerogear-android-cookbook/commit/0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff-7953a6ab3baf837d865c743a054cc357 [2] https://github.com/aerogear/aerogear-android-cookbook/commit/697cefdf60203200a2dc2aa89d60f0ed0418c715#diff-7953a6ab3baf837d865c743a054cc357L113 On Wed, Jan 18, 2017 at 7:08 PM, columfoskin wrote: > Hey all, > > I am working on building a Node js version of the backend for the Aerodoc > application and have some questions if anyone can help it would be great. > > Can anybody help me to understand when the lat/long pairs are sent from the > android device to the Aerodoc backend? I have spent some time debugging and > trying to figure this out - without much success. > > I have been looking at the request sent from the android app on login and > it > is not then. My guess from looking at the Java code is this happens when > when a HTTP PUT is called on the ?saleagents? endpoint but I cannot > determine when that endpoint is hit (from looking at the code & debugging). > > Also, from what I see, updates to the agents status are sending a POST to > the backend, and not a PUT and therefore hitting my POST endpoint - causing > issues. Is this expected behaviour? > > Any insight or help appreciated. > > Colum. > > > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Aerodoc-android-client-lat-long-issue- > updating-agent-status-issue-tp1013.html > Sent from the aerogear-users mailing list archive at Nabble.com. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/a45dfd90/attachment.html From kelvin at qantel.com Wed Jan 18 17:22:04 2017 From: kelvin at qantel.com (Kelvin Lunsford) Date: Wed, 18 Jan 2017 22:22:04 +0000 Subject: [Aerogear-users] Multiple aliases with the same token In-Reply-To: References: <1484212389700-1008.post@n5.nabble.com> <1484212436183-1009.post@n5.nabble.com> Message-ID: If you decide to use categories, be aware that the characters available for use in category names is more restricted than those available for alias names (i.e. "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789%-._~". If you want to use other characters in your names you will have to escape them in your own code (e.g. percent encoding like in a url). - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Wednesday, January 18, 2017 12:54 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] Multiple aliases with the same token not planed, we have categories, you can have multiple categories per device On Thu, Jan 12, 2017 at 10:13 AM, crysm > wrote: I was referring to the Unified Push Server. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Multiple-aliases-with-the-same-token-tp1008p1009.html Sent from the aerogear-users mailing list archive at Nabble.com. _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/87a5b8cc/attachment-0001.html From supittma at redhat.com Wed Jan 18 17:53:55 2017 From: supittma at redhat.com (Summers Pittman) Date: Wed, 18 Jan 2017 17:53:55 -0500 Subject: [Aerogear-users] Android SDK doesn't work, any way to debug? In-Reply-To: References: <1484129715269-1007.post@n5.nabble.com> Message-ID: Are you including the Google Services json file? On Wed, Jan 18, 2017 at 4:15 PM, Daniel Passos wrote: > Hi > > What version of UPS are you using? > > On Wed, Jan 11, 2017 at 8:15 AM, r00dY wrote: > >> Hi guys, >> >> I've implemented aerogear push in Titanium app, iOS native app, so far so >> good. Now need to integrate AG into Android and I'm struggling. >> >> Steps I've done: >> 1. Set up project and app in Firebase console. >> 2. (tested push notifications by native Firebase SDK - they worked). >> 3. I add to gradle following stuff: >> >> compile 'com.google.firebase:firebase-messaging:9.8.0' >> compile 'org.jboss.aerogear:aerogear-android-push:4.1.0' >> >> and use google-services plugin, version 3 >> >> 4. I create Aerogear Android variant, set up Google API key (tried legacy >> and new) and project ID from Firebase console (the ones that worked in a >> native way). >> 5. I register for pushes using AG SDK and registration is OK (see new >> device >> in admin panel). >> 6. I set up DEFAULT_MESSAGE_HANDLER_KEY variable. >> 7. I create message handler. >> 8. I send test push via "Send notification to this app" form. I set up >> text, >> the rest of fields is left to "All". >> 9. I get callback that push notification is successfully sent. >> 10. Nothing happens on my device (tried Android 5, 6 and 7). >> >> I was quite frustrated so I downloaded example project HelloPush >> https://github.com/aerogear/aerogear-android-cookbook/tree/ >> master/HelloPush, >> created for it new app in Firebase console and set up all configuration >> data >> from my AeroGear panel. Same thing happens. >> >> Any idea what may be the reason or do you have any methods for more >> detailed >> debugging like: >> 1. Debugging of internals in Aerogear SDK, some verbose logging etc. >> 2. Debugging what's going on between Aerogear and Firebase while sending >> push? Because I'm not sure if it's SDK fault or a fault of communication >> between Aerogear and Firebase. >> >> I can't wait for your answers, best! >> >> >> >> >> -- >> View this message in context: http://aerogear-users.1116366. >> n5.nabble.com/Android-SDK-doesn-t-work-any-way-to-debug-tp1007.html >> Sent from the aerogear-users mailing list archive at Nabble.com. >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > > -- > -- Passos > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170118/e517a541/attachment.html From benjamin.fras at petafuel.de Thu Jan 19 01:48:35 2017 From: benjamin.fras at petafuel.de (benjaminfras) Date: Wed, 18 Jan 2017 23:48:35 -0700 (MST) Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: References: <1484043518460-1004.post@n5.nabble.com> Message-ID: <1484808515067-1018.post@n5.nabble.com> Hi, thanks for looking into this matter. Yes, this only occurs with apple (see. https://gist.github.com/anonymous/b04ba972f02caaae0b9a031b37f0a1bd). It is not happening immediately after start, but after a week or so we get first notifications from our monitoring systems. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Many-established-connections-to-Apple-servers-tp1004p1018.html Sent from the aerogear-users mailing list archive at Nabble.com. From matzew at apache.org Thu Jan 19 02:08:26 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 08:08:26 +0100 Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: <1484808515067-1018.post@n5.nabble.com> References: <1484043518460-1004.post@n5.nabble.com> <1484808515067-1018.post@n5.nabble.com> Message-ID: Ok, good - we willt ake a look, On Thu, Jan 19, 2017 at 7:48 AM, benjaminfras wrote: > Hi, > thanks for looking into this matter. Yes, this only occurs with apple (see. > https://gist.github.com/anonymous/b04ba972f02caaae0b9a031b37f0a1bd). > > It is not happening immediately after start, but after a week or so we get > first notifications from our monitoring systems. > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Many-established-connections-to- > Apple-servers-tp1004p1018.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/71c36813/attachment.html From edewit at redhat.com Thu Jan 19 02:45:17 2017 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 19 Jan 2017 08:45:17 +0100 Subject: [Aerogear-users] Android SDK doesn't work, any way to debug? In-Reply-To: References: <1484129715269-1007.post@n5.nabble.com> Message-ID: For Titanium we have a plugin as well: https://github.com/Napp/AeroGear-Push-Titanium that uses https://github.com/aerogear/aerogear-titanium-push and https://github.com/feedhenry-templates/pushstarter-titanium-app is an app that uses these plugins, maybe this helps On Wed, Jan 18, 2017 at 11:53 PM, Summers Pittman wrote: > Are you including the Google Services json file? > > On Wed, Jan 18, 2017 at 4:15 PM, Daniel Passos wrote: > >> Hi >> >> What version of UPS are you using? >> >> On Wed, Jan 11, 2017 at 8:15 AM, r00dY wrote: >> >>> Hi guys, >>> >>> I've implemented aerogear push in Titanium app, iOS native app, so far so >>> good. Now need to integrate AG into Android and I'm struggling. >>> >>> Steps I've done: >>> 1. Set up project and app in Firebase console. >>> 2. (tested push notifications by native Firebase SDK - they worked). >>> 3. I add to gradle following stuff: >>> >>> compile 'com.google.firebase:firebase-messaging:9.8.0' >>> compile 'org.jboss.aerogear:aerogear-android-push:4.1.0' >>> >>> and use google-services plugin, version 3 >>> >>> 4. I create Aerogear Android variant, set up Google API key (tried legacy >>> and new) and project ID from Firebase console (the ones that worked in a >>> native way). >>> 5. I register for pushes using AG SDK and registration is OK (see new >>> device >>> in admin panel). >>> 6. I set up DEFAULT_MESSAGE_HANDLER_KEY variable. >>> 7. I create message handler. >>> 8. I send test push via "Send notification to this app" form. I set up >>> text, >>> the rest of fields is left to "All". >>> 9. I get callback that push notification is successfully sent. >>> 10. Nothing happens on my device (tried Android 5, 6 and 7). >>> >>> I was quite frustrated so I downloaded example project HelloPush >>> https://github.com/aerogear/aerogear-android-cookbook/tree/m >>> aster/HelloPush, >>> created for it new app in Firebase console and set up all configuration >>> data >>> from my AeroGear panel. Same thing happens. >>> >>> Any idea what may be the reason or do you have any methods for more >>> detailed >>> debugging like: >>> 1. Debugging of internals in Aerogear SDK, some verbose logging etc. >>> 2. Debugging what's going on between Aerogear and Firebase while sending >>> push? Because I'm not sure if it's SDK fault or a fault of communication >>> between Aerogear and Firebase. >>> >>> I can't wait for your answers, best! >>> >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Android-SDK-doesn-t-work-any-way-to-debug-tp1007.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/1061de57/attachment-0001.html From matzew at apache.org Thu Jan 19 03:07:37 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 09:07:37 +0100 Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: References: <1484043518460-1004.post@n5.nabble.com> <1484808515067-1018.post@n5.nabble.com> Message-ID: Hey Ben, we have this ticket: https://issues.jboss.org/browse/AGPUSH-2011 and will include it in a set of tests, that we run. Stay tuned - sorry for the inconvenience. On Thu, Jan 19, 2017 at 8:08 AM, Matthias Wessendorf wrote: > Ok, good - we willt ake a look, > > > > On Thu, Jan 19, 2017 at 7:48 AM, benjaminfras > wrote: > >> Hi, >> thanks for looking into this matter. Yes, this only occurs with apple >> (see. >> https://gist.github.com/anonymous/b04ba972f02caaae0b9a031b37f0a1bd). >> >> It is not happening immediately after start, but after a week or so we get >> first notifications from our monitoring systems. >> >> >> >> -- >> View this message in context: http://aerogear-users.1116366. >> n5.nabble.com/Many-established-connections-to-Apple-servers- >> tp1004p1018.html >> Sent from the aerogear-users mailing list archive at Nabble.com. >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/93d8ecdd/attachment.html From matzew at apache.org Thu Jan 19 03:09:01 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 09:09:01 +0100 Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: References: <1484773734164-1013.post@n5.nabble.com> Message-ID: Why was this removed? It's a key part of the demo. Not sure I recall any discussion around removing this :-( On Wed, Jan 18, 2017 at 10:22 PM, Daniel Passos wrote: > Hi, > > This features was removed[1] by me. For more details here[2] is where > magic happened > > [1] > https://github.com/aerogear/aerogear-android-cookbook/commit/ > 0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff- > 7953a6ab3baf837d865c743a054cc357 > [2] https://github.com/aerogear/aerogear-android-cookbook/commit/ > 697cefdf60203200a2dc2aa89d60f0ed0418c715#diff- > 7953a6ab3baf837d865c743a054cc357L113 > > > On Wed, Jan 18, 2017 at 7:08 PM, columfoskin > wrote: > >> Hey all, >> >> I am working on building a Node js version of the backend for the Aerodoc >> application and have some questions if anyone can help it would be great. >> >> Can anybody help me to understand when the lat/long pairs are sent from >> the >> android device to the Aerodoc backend? I have spent some time debugging >> and >> trying to figure this out - without much success. >> >> I have been looking at the request sent from the android app on login and >> it >> is not then. My guess from looking at the Java code is this happens when >> when a HTTP PUT is called on the ?saleagents? endpoint but I cannot >> determine when that endpoint is hit (from looking at the code & >> debugging). >> >> Also, from what I see, updates to the agents status are sending a POST to >> the backend, and not a PUT and therefore hitting my POST endpoint - >> causing >> issues. Is this expected behaviour? >> >> Any insight or help appreciated. >> >> Colum. >> >> >> >> >> >> -- >> View this message in context: http://aerogear-users.1116366. >> n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating >> -agent-status-issue-tp1013.html >> Sent from the aerogear-users mailing list archive at Nabble.com. >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > > -- > -- Passos > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/f39f7af8/attachment.html From matzew at apache.org Thu Jan 19 03:18:32 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 09:18:32 +0100 Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: References: <1484773734164-1013.post@n5.nabble.com> Message-ID: @Colum, if you have interest, feel free to put together a PR for adding the tracking back :-) On Thu, Jan 19, 2017 at 9:09 AM, Matthias Wessendorf wrote: > Why was this removed? It's a key part of the demo. Not sure I recall any > discussion around removing this :-( > > On Wed, Jan 18, 2017 at 10:22 PM, Daniel Passos > wrote: > >> Hi, >> >> This features was removed[1] by me. For more details here[2] is where >> magic happened >> >> [1] >> https://github.com/aerogear/aerogear-android-cookbook/commit >> /0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff-7953a6ab3baf8 >> 37d865c743a054cc357 >> [2] https://github.com/aerogear/aerogear-android-cookbook/commit >> /697cefdf60203200a2dc2aa89d60f0ed0418c715#diff-7953a6ab3baf8 >> 37d865c743a054cc357L113 >> >> >> On Wed, Jan 18, 2017 at 7:08 PM, columfoskin >> wrote: >> >>> Hey all, >>> >>> I am working on building a Node js version of the backend for the Aerodoc >>> application and have some questions if anyone can help it would be great. >>> >>> Can anybody help me to understand when the lat/long pairs are sent from >>> the >>> android device to the Aerodoc backend? I have spent some time debugging >>> and >>> trying to figure this out - without much success. >>> >>> I have been looking at the request sent from the android app on login >>> and it >>> is not then. My guess from looking at the Java code is this happens when >>> when a HTTP PUT is called on the ?saleagents? endpoint but I cannot >>> determine when that endpoint is hit (from looking at the code & >>> debugging). >>> >>> Also, from what I see, updates to the agents status are sending a POST to >>> the backend, and not a PUT and therefore hitting my POST endpoint - >>> causing >>> issues. Is this expected behaviour? >>> >>> Any insight or help appreciated. >>> >>> Colum. >>> >>> >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating >>> -agent-status-issue-tp1013.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/3895e98e/attachment-0001.html From columfoskin at gmail.com Thu Jan 19 04:51:47 2017 From: columfoskin at gmail.com (columfoskin) Date: Thu, 19 Jan 2017 02:51:47 -0700 (MST) Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: References: <1484773734164-1013.post@n5.nabble.com> Message-ID: <1484819507525-1024.post@n5.nabble.com> Hi Daniel. Is there specific reasons as to why it was removed? Also - is there much involved in getting this feature added back in, is it just a case of reverting back to the commit you have posted? Thanks, Colum. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating-agent-status-issue-tp1013p1024.html Sent from the aerogear-users mailing list archive at Nabble.com. From a.r.dabrowski at gmail.com Thu Jan 19 05:02:13 2017 From: a.r.dabrowski at gmail.com (r00dY) Date: Thu, 19 Jan 2017 03:02:13 -0700 (MST) Subject: [Aerogear-users] Android SDK doesn't work, any way to debug? In-Reply-To: References: <1484129715269-1007.post@n5.nabble.com> Message-ID: <1484820133210-1025.post@n5.nabble.com> Hi Daniel thanks for your response. We're currently using 1.1.0 version. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-SDK-doesn-t-work-any-way-to-debug-tp1007p1025.html Sent from the aerogear-users mailing list archive at Nabble.com. From dpassos at redhat.com Thu Jan 19 07:25:11 2017 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 19 Jan 2017 10:25:11 -0200 Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: References: <1484773734164-1013.post@n5.nabble.com> Message-ID: I have removed it because it doesn't work with Firebase + Android N. Just created a issues to fix that problem and add it back. https://issues.jboss.org/browse/AGDROID-599 On Thu, Jan 19, 2017 at 6:09 AM, Matthias Wessendorf wrote: > Why was this removed? It's a key part of the demo. Not sure I recall any > discussion around removing this :-( > > On Wed, Jan 18, 2017 at 10:22 PM, Daniel Passos > wrote: > >> Hi, >> >> This features was removed[1] by me. For more details here[2] is where >> magic happened >> >> [1] >> https://github.com/aerogear/aerogear-android-cookbook/commit >> /0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff-7953a6ab3baf8 >> 37d865c743a054cc357 >> [2] https://github.com/aerogear/aerogear-android-cookbook/commit >> /697cefdf60203200a2dc2aa89d60f0ed0418c715#diff-7953a6ab3baf8 >> 37d865c743a054cc357L113 >> >> >> On Wed, Jan 18, 2017 at 7:08 PM, columfoskin >> wrote: >> >>> Hey all, >>> >>> I am working on building a Node js version of the backend for the Aerodoc >>> application and have some questions if anyone can help it would be great. >>> >>> Can anybody help me to understand when the lat/long pairs are sent from >>> the >>> android device to the Aerodoc backend? I have spent some time debugging >>> and >>> trying to figure this out - without much success. >>> >>> I have been looking at the request sent from the android app on login >>> and it >>> is not then. My guess from looking at the Java code is this happens when >>> when a HTTP PUT is called on the ?saleagents? endpoint but I cannot >>> determine when that endpoint is hit (from looking at the code & >>> debugging). >>> >>> Also, from what I see, updates to the agents status are sending a POST to >>> the backend, and not a PUT and therefore hitting my POST endpoint - >>> causing >>> issues. Is this expected behaviour? >>> >>> Any insight or help appreciated. >>> >>> Colum. >>> >>> >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating >>> -agent-status-issue-tp1013.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> >> -- >> -- Passos >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/02e889ab/attachment.html From matzew at apache.org Thu Jan 19 07:55:51 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 13:55:51 +0100 Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: References: <1484773734164-1013.post@n5.nabble.com> Message-ID: ah, great! ? Colum, interested? ? On Thursday, 19 January 2017, Daniel Passos wrote: > I have removed it because it doesn't work with Firebase + Android N. > > Just created a issues to fix that problem and add it back. > > https://issues.jboss.org/browse/AGDROID-599 > > On Thu, Jan 19, 2017 at 6:09 AM, Matthias Wessendorf > wrote: > >> Why was this removed? It's a key part of the demo. Not sure I recall any >> discussion around removing this :-( >> >> On Wed, Jan 18, 2017 at 10:22 PM, Daniel Passos > > wrote: >> >>> Hi, >>> >>> This features was removed[1] by me. For more details here[2] is where >>> magic happened >>> >>> [1] >>> https://github.com/aerogear/aerogear-android-cookbook/commit >>> /0331d7d0b2c33e0bffefacd5102ed811024beb9f#diff-7953a6ab3baf8 >>> 37d865c743a054cc357 >>> [2] https://github.com/aerogear/aerogear-android-cookbook/commit >>> /697cefdf60203200a2dc2aa89d60f0ed0418c715#diff-7953a6ab3baf8 >>> 37d865c743a054cc357L113 >>> >>> >>> On Wed, Jan 18, 2017 at 7:08 PM, columfoskin >> > wrote: >>> >>>> Hey all, >>>> >>>> I am working on building a Node js version of the backend for the >>>> Aerodoc >>>> application and have some questions if anyone can help it would be >>>> great. >>>> >>>> Can anybody help me to understand when the lat/long pairs are sent from >>>> the >>>> android device to the Aerodoc backend? I have spent some time debugging >>>> and >>>> trying to figure this out - without much success. >>>> >>>> I have been looking at the request sent from the android app on login >>>> and it >>>> is not then. My guess from looking at the Java code is this happens when >>>> when a HTTP PUT is called on the ?saleagents? endpoint but I cannot >>>> determine when that endpoint is hit (from looking at the code & >>>> debugging). >>>> >>>> Also, from what I see, updates to the agents status are sending a POST >>>> to >>>> the backend, and not a PUT and therefore hitting my POST endpoint - >>>> causing >>>> issues. Is this expected behaviour? >>>> >>>> Any insight or help appreciated. >>>> >>>> Colum. >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://aerogear-users.1116366. >>>> n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating >>>> -agent-status-issue-tp1013.html >>>> Sent from the aerogear-users mailing list archive at Nabble.com. >>>> >>>> _______________________________________________ >>>> Aerogear-users mailing list >>>> Aerogear-users at lists.jboss.org >>>> >>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>> >>> >>> >>> >>> -- >>> -- Passos >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >>> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> twitter: http://twitter.com/mwessendorf >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > -- Passos > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/aa9d51c7/attachment.html From matzew at apache.org Thu Jan 19 08:22:01 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 14:22:01 +0100 Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: References: <1484043518460-1004.post@n5.nabble.com> <1484808515067-1018.post@n5.nabble.com> Message-ID: btw. what version are you guys using ? On Thu, Jan 19, 2017 at 9:07 AM, Matthias Wessendorf wrote: > Hey Ben, > > we have this ticket: > https://issues.jboss.org/browse/AGPUSH-2011 > > and will include it in a set of tests, that we run. Stay tuned - sorry for > the inconvenience. > > On Thu, Jan 19, 2017 at 8:08 AM, Matthias Wessendorf > wrote: > >> Ok, good - we willt ake a look, >> >> >> >> On Thu, Jan 19, 2017 at 7:48 AM, benjaminfras >> wrote: >> >>> Hi, >>> thanks for looking into this matter. Yes, this only occurs with apple >>> (see. >>> https://gist.github.com/anonymous/b04ba972f02caaae0b9a031b37f0a1bd). >>> >>> It is not happening immediately after start, but after a week or so we >>> get >>> first notifications from our monitoring systems. >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Many-established-connections-to-Apple-servers- >>> tp1004p1018.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> twitter: http://twitter.com/mwessendorf >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > twitter: http://twitter.com/mwessendorf > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/3fbc65d9/attachment-0001.html From antonio.falcone at cg.tasgroup.it Thu Jan 19 09:41:09 2017 From: antonio.falcone at cg.tasgroup.it (falconea) Date: Thu, 19 Jan 2017 07:41:09 -0700 (MST) Subject: [Aerogear-users] Open specific page on notification received Message-ID: <1484836869934-1029.post@n5.nabble.com> Hello, I would like to open a specific page in my cordova application once a notification is received. How can i do that? Also, I am sending additional informations with my notification such as ("person_id" "xxx_xxx"), with .userData("some_key", "with_value"). How do I read this informations in my hibrid application? I did not find these informations on documentation. Thank you. Antonio -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Open-specific-page-on-notification-received-tp1029.html Sent from the aerogear-users mailing list archive at Nabble.com. From supittma at redhat.com Thu Jan 19 10:00:32 2017 From: supittma at redhat.com (Summers Pittman) Date: Thu, 19 Jan 2017 10:00:32 -0500 Subject: [Aerogear-users] Open specific page on notification received In-Reply-To: <1484836869934-1029.post@n5.nabble.com> References: <1484836869934-1029.post@n5.nabble.com> Message-ID: This is all done with the notification callback you send to push.register. See https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/#_sample_example for details. The argument your callback is passed should have all of the properties of the message sent from UPS in it. On Thu, Jan 19, 2017 at 9:41 AM, falconea wrote: > Hello, I would like to open a specific page in my cordova application once > a > notification is received. How can i do that? > Also, I am sending additional informations with my notification such as > ("person_id" "xxx_xxx"), with .userData("some_key", "with_value"). > How do I read this informations in my hibrid application? I did not find > these informations on documentation. > > Thank you. > > Antonio > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Open-specific-page-on-notification-received-tp1029.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/25954171/attachment.html From benjamin.fras at petafuel.de Thu Jan 19 10:16:07 2017 From: benjamin.fras at petafuel.de (benjaminfras) Date: Thu, 19 Jan 2017 08:16:07 -0700 (MST) Subject: [Aerogear-users] Many established connections to Apple servers In-Reply-To: References: <1484043518460-1004.post@n5.nabble.com> <1484808515067-1018.post@n5.nabble.com> Message-ID: <1484838967509-1031.post@n5.nabble.com> we're using version 1.1.3.Final. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Many-established-connections-to-Apple-servers-tp1004p1031.html Sent from the aerogear-users mailing list archive at Nabble.com. From columfoskin at gmail.com Thu Jan 19 13:54:25 2017 From: columfoskin at gmail.com (columfoskin) Date: Thu, 19 Jan 2017 11:54:25 -0700 (MST) Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: References: <1484773734164-1013.post@n5.nabble.com> Message-ID: <1484852065648-1032.post@n5.nabble.com> Hey Matthias, Its not that I am not interested, but I am really busy trying to get the node backend complete in the next week or so, before even looking into microservices! I am starting several other college projects in the next week or so too, so I couldn't really prioritise the android fix over my college work. I need to manage my time carefully over the next few weeks or so! Colum. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerodoc-android-client-lat-long-issue-updating-agent-status-issue-tp1013p1032.html Sent from the aerogear-users mailing list archive at Nabble.com. From matzew at apache.org Thu Jan 19 14:25:15 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 19 Jan 2017 20:25:15 +0100 Subject: [Aerogear-users] Aerodoc android client lat/long issue & updating agent status issue In-Reply-To: <1484852065648-1032.post@n5.nabble.com> References: <1484773734164-1013.post@n5.nabble.com> <1484852065648-1032.post@n5.nabble.com> Message-ID: sure, don't worry :-) On Thu, Jan 19, 2017 at 7:54 PM, columfoskin wrote: > Hey Matthias, > > Its not that I am not interested, but I am really busy trying to get the > node backend complete in the next week or so, before even looking into > microservices! > > I am starting several other college projects in the next week or so too, so > I couldn't really prioritise the android fix over my college work. I need > to > manage my time carefully over the next few weeks or so! > > Colum. > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Aerodoc-android-client-lat-long-issue- > updating-agent-status-issue-tp1013p1032.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170119/beb02630/attachment.html From edewit at redhat.com Fri Jan 20 03:00:13 2017 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 20 Jan 2017 09:00:13 +0100 Subject: [Aerogear-users] Open specific page on notification received In-Reply-To: References: <1484836869934-1029.post@n5.nabble.com> Message-ID: Like Summers said it?s in the argument passed in the callback, but I wanted to make it even more clear with an example: so if you send a message like this: curl -u "00000-0000-0000-0000-000:00-0000" \ -v -H "Accept: application/json" -H "Content-type: application/json" \ -X POST -d \ '{ "message": { "alert": "Hello ", "user-data": { "test": "I am the user data" } } }' \ https://ups-youraccount.rhcloud.com/ag-push/rest/sender Then you can read the test data in your js callback like this: push.register(onNotification, successHandler, errorHandler);//... function onNotification(message) { console.log("user data send: " + message.payload.test); // will produce: "user data send: I am the user data" console.log("alert message " + message.alert); } Hope that makes things even more clear ? On Thu, Jan 19, 2017 at 4:00 PM, Summers Pittman wrote: > This is all done with the notification callback you send to push.register. > > See https://aerogear.org/docs/guides/aerogear-cordova/ > AerogearCordovaPush/#_sample_example for details. > > The argument your callback is passed should have all of the properties of > the message sent from UPS in it. > > On Thu, Jan 19, 2017 at 9:41 AM, falconea > wrote: > >> Hello, I would like to open a specific page in my cordova application >> once a >> notification is received. How can i do that? >> Also, I am sending additional informations with my notification such as >> ("person_id" "xxx_xxx"), with .userData("some_key", "with_value"). >> How do I read this informations in my hibrid application? I did not find >> these informations on documentation. >> >> Thank you. >> >> Antonio >> >> >> >> -- >> View this message in context: http://aerogear-users.1116366. >> n5.nabble.com/Open-specific-page-on-notification-received-tp1029.html >> Sent from the aerogear-users mailing list archive at Nabble.com. >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170120/4c57a092/attachment-0001.html From antonio.falcone at cg.tasgroup.it Fri Jan 20 04:09:58 2017 From: antonio.falcone at cg.tasgroup.it (falconea) Date: Fri, 20 Jan 2017 02:09:58 -0700 (MST) Subject: [Aerogear-users] Open specific page on notification received In-Reply-To: References: <1484836869934-1029.post@n5.nabble.com> Message-ID: <1484903398818-1035.post@n5.nabble.com> Ok now it's more clear. In order to open a new page on notification opened, i can set window.location="page2.html" in onNotification method? @erik, sorry for the private message. i did want to post here, it was a mistake :) Erik Jan de Wit wrote > Like Summers said it?s in the argument passed in the callback, but I > wanted > to make it even more clear with an example: > > so if you send a message like this: > > curl -u "00000-0000-0000-0000-000:00-0000" \ > -v -H "Accept: application/json" -H "Content-type: application/json" \ > -X POST -d \ > '{ > "message": { > "alert": "Hello ", > "user-data": { > "test": "I am the user data" > } > } > }' \ > https://ups-youraccount.rhcloud.com/ag-push/rest/sender > > Then you can read the test data in your js callback like this: > > push.register(onNotification, successHandler, errorHandler);//... > function onNotification(message) { > console.log("user data send: " + message.payload.test); // will > produce: "user data send: I am the user data" > console.log("alert message " + message.alert); > } > > Hope that makes things even more clear > ? > > On Thu, Jan 19, 2017 at 4:00 PM, Summers Pittman < > supittma@ > > > wrote: > >> This is all done with the notification callback you send to >> push.register. >> >> See https://aerogear.org/docs/guides/aerogear-cordova/ >> AerogearCordovaPush/#_sample_example for details. >> >> The argument your callback is passed should have all of the properties of >> the message sent from UPS in it. >> >> On Thu, Jan 19, 2017 at 9:41 AM, falconea < > antonio.falcone at .tasgroup > > >> wrote: >> >>> Hello, I would like to open a specific page in my cordova application >>> once a >>> notification is received. How can i do that? >>> Also, I am sending additional informations with my notification such as >>> ("person_id" "xxx_xxx"), with .userData("some_key", "with_value"). >>> How do I read this informations in my hibrid application? I did not find >>> these informations on documentation. >>> >>> Thank you. >>> >>> Antonio >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Open-specific-page-on-notification-received-tp1029.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> _______________________________________________ >>> Aerogear-users mailing list >>> > Aerogear-users at .jboss >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> _______________________________________________ >> Aerogear-users mailing list >> > Aerogear-users at .jboss >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Cheers, > Erik Jan > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at .jboss > https://lists.jboss.org/mailman/listinfo/aerogear-users -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Open-specific-page-on-notification-received-tp1029p1035.html Sent from the aerogear-users mailing list archive at Nabble.com. From edewit at redhat.com Fri Jan 20 08:51:30 2017 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 20 Jan 2017 14:51:30 +0100 Subject: [Aerogear-users] Open specific page on notification received In-Reply-To: <1484903398818-1035.post@n5.nabble.com> References: <1484836869934-1029.post@n5.nabble.com> <1484903398818-1035.post@n5.nabble.com> Message-ID: > > Ok now it's more clear. In order to open a new page on notification > opened, i > can set window.location="page2.html" in onNotification method? > > You could, although I would suggest using a javascript framework to write your client app -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170120/a48ad4ce/attachment.html From antonio.falcone at cg.tasgroup.it Fri Jan 20 09:56:42 2017 From: antonio.falcone at cg.tasgroup.it (falconea) Date: Fri, 20 Jan 2017 07:56:42 -0700 (MST) Subject: [Aerogear-users] Open specific page on notification received In-Reply-To: References: <1484836869934-1029.post@n5.nabble.com> <1484903398818-1035.post@n5.nabble.com> Message-ID: <1484924202663-1037.post@n5.nabble.com> I am using jQuery. Do you suggest something else than window.location ? Erik Jan de Wit wrote >> >> You could, although I would suggest using a javascript framework to write > your client app > > -- > Cheers, > Erik Jan > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at .jboss > https://lists.jboss.org/mailman/listinfo/aerogear-users -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Open-specific-page-on-notification-received-tp1029p1037.html Sent from the aerogear-users mailing list archive at Nabble.com. From edewit at redhat.com Fri Jan 20 11:23:18 2017 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 20 Jan 2017 17:23:18 +0100 Subject: [Aerogear-users] Open specific page on notification received In-Reply-To: <1484924202663-1037.post@n5.nabble.com> References: <1484836869934-1029.post@n5.nabble.com> <1484903398818-1035.post@n5.nabble.com> <1484924202663-1037.post@n5.nabble.com> Message-ID: It's a mobile app, so something with page transition would be nice, if you are using jQuery why not have a look at how jQuery mobile is doing page transitions. But feel free to do a simple window.location that will work as well. On Fri, Jan 20, 2017 at 3:56 PM, falconea wrote: > I am using jQuery. Do you suggest something else than window.location ? > > > Erik Jan de Wit wrote > >> > >> You could, although I would suggest using a javascript framework to > write > > your client app > > > > -- > > Cheers, > > Erik Jan > > > > _______________________________________________ > > Aerogear-users mailing list > > > Aerogear-users at .jboss > > > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Open-specific-page-on-notification-received-tp1029p1037.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170120/2924ef2e/attachment.html From a.r.dabrowski at gmail.com Thu Jan 26 08:03:23 2017 From: a.r.dabrowski at gmail.com (r00dY) Date: Thu, 26 Jan 2017 06:03:23 -0700 (MST) Subject: [Aerogear-users] Android SDK doesn't work, any way to debug? In-Reply-To: <1484820133210-1025.post@n5.nabble.com> References: <1484129715269-1007.post@n5.nabble.com> <1484820133210-1025.post@n5.nabble.com> Message-ID: <1485435803991-1041.post@n5.nabble.com> Didn't do anything and checked the same code again today. Everything works. Weird but I'm happy. Thanks guys for your replies! -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-SDK-doesn-t-work-any-way-to-debug-tp1007p1041.html Sent from the aerogear-users mailing list archive at Nabble.com. From antonio.falcone at cg.tasgroup.it Fri Jan 27 09:12:31 2017 From: antonio.falcone at cg.tasgroup.it (falconea) Date: Fri, 27 Jan 2017 07:12:31 -0700 (MST) Subject: [Aerogear-users] onNotification not always triggered Message-ID: <1485526351265-1042.post@n5.nabble.com> I have my onNotification function, integrated in my Framework 7 client app: onNotification: function(message) { mainView.router.loadContent($('#pay').html()); $('#iuv').html(message.payload.number); //myApp.alert('number: ' + message.payload.number, 'Mobile'); } The problem is that function is not triggered on all notifications. Sometime nothing happens. Metrics are not sent to Unifiedpush console too. onDeviceReady: function() { pushInit.receivedEvent('deviceready'); var pushConfig = { pushServerURL: "http://10.1.42.249:8080/ag-push/", sendMetricInfo: true, android: { senderID: "1.0", variantID: "20010eaa-a3be-474a-84a9-e98fdf57e7f9", variantSecret: "94706157-5189-437e-b9a0-3800c934ddea" } }; Do you have any idea to solve this problem? -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/onNotification-not-always-triggered-tp1042.html Sent from the aerogear-users mailing list archive at Nabble.com. From David.Walto at baystatehealth.org Fri Jan 27 16:22:19 2017 From: David.Walto at baystatehealth.org (Walto, David) Date: Fri, 27 Jan 2017 16:22:19 -0500 Subject: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days Message-ID: <0BBC8B85145220449B53DE768FDA802A2A40FAADF7@bhsexc12.bhs.org> We have an AeroGear UnifiedPush Server 1.1.3 that goes idle every couple of days. If a device tries to register when it's idle the registration fails. The only way I found to wake it up is to restart it. Is there something I can change to prevent it from going to the Idle state? Thanks, David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 ---------------------------------------------------------------------- Please view our annual report at http://www.bhannualreport.org CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at https://www.baystatehealth.org. From matzew at apache.org Fri Jan 27 17:18:30 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 27 Jan 2017 23:18:30 +0100 Subject: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days In-Reply-To: <0BBC8B85145220449B53DE768FDA802A2A40FAADF7@bhsexc12.bhs.org> References: <0BBC8B85145220449B53DE768FDA802A2A40FAADF7@bhsexc12.bhs.org> Message-ID: any logs? or stack trace? whats the size of the variant? number iof devices? On Friday, 27 January 2017, Walto, David wrote: > We have an AeroGear UnifiedPush Server 1.1.3 that goes idle every couple > of days. If a device tries to register when it's idle the registration > fails. The only way I found to wake it up is to restart it. Is there > something I can change to prevent it from going to the Idle state? > > Thanks, > David Walto > Senior Application Engineer | EMR Engineering and Integration > Baystate Health | Information & Technology > 1550 Main Street, Springfield, MA 01199 > > ---------------------------------------------------------------------- > Please view our annual report at http://www.bhannualreport.org > > > CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may > contain confidential and privileged information for the use of the > designated recipients named above. If you are not the intended recipient, > you are hereby notified that you have received this communication in error > and that any review, disclosure, dissemination, distribution or copying of > it or its contents is prohibited. If you have received this communication > in error, please reply to the sender immediately or by telephone at > 413-794-0000 and destroy all copies of this communication and any > attachments. For further information regarding Baystate Health's privacy > policy, please visit our Internet site at https://www.baystatehealth.org. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170127/27b09b8e/attachment-0001.html From David.Walto at baystatehealth.org Tue Jan 31 07:51:41 2017 From: David.Walto at baystatehealth.org (Walto, David) Date: Tue, 31 Jan 2017 07:51:41 -0500 Subject: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days In-Reply-To: References: <0BBC8B85145220449B53DE768FDA802A2A40FAADF7@bhsexc12.bhs.org> Message-ID: <0BBC8B85145220449B53DE768FDA802A2A40FAB190@bhsexc12.bhs.org> Are there any logs I can look at on OpenShift? If so where are they. I only have about 2 variants and 8 devices registered. I haven?t been able to move this to production because it of the idle issue. Every couple of days this is what I get, and to wake it up I need to restart it. [cid:image001.jpg at 01D27B96.DC194480] Thanks, David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: 413-794-5570 From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Friday, January 27, 2017 5:19 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days any logs? or stack trace? whats the size of the variant? number iof devices? On Friday, 27 January 2017, Walto, David > wrote: We have an AeroGear UnifiedPush Server 1.1.3 that goes idle every couple of days. If a device tries to register when it's idle the registration fails. The only way I found to wake it up is to restart it. Is there something I can change to prevent it from going to the Idle state? Thanks, David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 ---------------------------------------------------------------------- Please view our annual report at http://www.bhannualreport.org CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at https://www.baystatehealth.org. _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Sent from Gmail Mobile ---------------------------------------------------------------------- Please view our annual report at http://www.bhannualreport.org CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at https://www.baystatehealth.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170131/706c300a/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4000 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20170131/706c300a/attachment.jpg From matzew at apache.org Tue Jan 31 08:15:24 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 31 Jan 2017 14:15:24 +0100 Subject: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days In-Reply-To: <0BBC8B85145220449B53DE768FDA802A2A40FAB190@bhsexc12.bhs.org> References: <0BBC8B85145220449B53DE768FDA802A2A40FAADF7@bhsexc12.bhs.org> <0BBC8B85145220449B53DE768FDA802A2A40FAB190@bhsexc12.bhs.org> Message-ID: ah, that's a feature on Openshift - if there is no activity, after 48 hours (I think) the gear goes idle. as a work-around, create a cron, doing a simple http-get ping? would that be OK ? On Tue, Jan 31, 2017 at 1:51 PM, Walto, David < David.Walto at baystatehealth.org> wrote: > Are there any logs I can look at on OpenShift? If so where are they. I > only have about 2 variants and 8 devices registered. I haven?t been able > to move this to production because it of the idle issue. > > > > Every couple of days this is what I get, and to wake it up I need to > restart it. > > > > Thanks, > > *David Walto* > > *Senior Application Engineer | EMR Engineering and Integration* > > *Baystate Health | Information & Technology* > > 1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: > 413-794-5570 > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* Friday, January 27, 2017 5:19 PM > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes > idle every couple of days > > > > any logs? or stack trace? > > whats the size of the variant? number iof devices? > > On Friday, 27 January 2017, Walto, David > wrote: > > We have an AeroGear UnifiedPush Server 1.1.3 that goes idle every couple > of days. If a device tries to register when it's idle the registration > fails. The only way I found to wake it up is to restart it. Is there > something I can change to prevent it from going to the Idle state? > > Thanks, > David Walto > Senior Application Engineer | EMR Engineering and Integration > Baystate Health | Information & Technology > 1550 Main Street, Springfield, MA 01199 > > ---------------------------------------------------------------------- > Please view our annual report at http://www.bhannualreport.org > > > > CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may > contain confidential and privileged information for the use of the > designated recipients named above. If you are not the intended recipient, > you are hereby notified that you have received this communication in error > and that any review, disclosure, dissemination, distribution or copying of > it or its contents is prohibited. If you have received this communication > in error, please reply to the sender immediately or by telephone at > 413-794-0000 and destroy all copies of this communication and any > attachments. For further information regarding Baystate Health's privacy > policy, please visit our Internet site at https://www.baystatehealth.org. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > -- > Sent from Gmail Mobile > ------------------------------ > Please view our annual report at http://www.bhannualreport.org > > > CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may > contain confidential and privileged information for the use of the > designated recipients named above. If you are not the intended recipient, > you are hereby notified that you have received this communication in error > and that any review, disclosure, dissemination, distribution or copying of > it or its contents is prohibited. If you have received this communication > in error, please reply to the sender immediately or by telephone at > 413-794-0000 and destroy all copies of this communication and any > attachments. For further information regarding Baystate Health's privacy > policy, please visit our Internet site at https://www.baystatehealth.org. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170131/e1f79e53/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4000 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20170131/e1f79e53/attachment-0001.jpg From David.Walto at baystatehealth.org Tue Jan 31 08:25:47 2017 From: David.Walto at baystatehealth.org (Walto, David) Date: Tue, 31 Jan 2017 08:25:47 -0500 Subject: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days In-Reply-To: References: <0BBC8B85145220449B53DE768FDA802A2A40FAADF7@bhsexc12.bhs.org> <0BBC8B85145220449B53DE768FDA802A2A40FAB190@bhsexc12.bhs.org> Message-ID: <0BBC8B85145220449B53DE768FDA802A2A40FAB1B2@bhsexc12.bhs.org> I can do that, thanks! David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: 413-794-5570 From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Tuesday, January 31, 2017 8:15 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days ah, that's a feature on Openshift - if there is no activity, after 48 hours (I think) the gear goes idle. as a work-around, create a cron, doing a simple http-get ping? would that be OK ? On Tue, Jan 31, 2017 at 1:51 PM, Walto, David > wrote: Are there any logs I can look at on OpenShift? If so where are they. I only have about 2 variants and 8 devices registered. I haven?t been able to move this to production because it of the idle issue. Every couple of days this is what I get, and to wake it up I need to restart it. [cid:image001.jpg at 01D27B9B.9F99A680] Thanks, David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: 413-794-5570 From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Friday, January 27, 2017 5:19 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] AeroGear UnifiedPush Server 1.1.3 goes idle every couple of days any logs? or stack trace? whats the size of the variant? number iof devices? On Friday, 27 January 2017, Walto, David > wrote: We have an AeroGear UnifiedPush Server 1.1.3 that goes idle every couple of days. If a device tries to register when it's idle the registration fails. The only way I found to wake it up is to restart it. Is there something I can change to prevent it from going to the Idle state? Thanks, David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 ---------------------------------------------------------------------- Please view our annual report at http://www.bhannualreport.org CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at https://www.baystatehealth.org. _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Sent from Gmail Mobile ________________________________ Please view our annual report at http://www.bhannualreport.org CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at https://www.baystatehealth.org. _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf ---------------------------------------------------------------------- Please view our annual report at http://www.bhannualreport.org CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at https://www.baystatehealth.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170131/448d2ef8/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4000 bytes Desc: image001.jpg Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20170131/448d2ef8/attachment-0001.jpg