I think I understood...
I hope you understand too what I'm trying to say: since I started with Aerogear some
months ago I was warned about this situation.
This is a recurring problem. Maybe there are already many logs reporting it...
Anyway, as you may know, when I can I try to send all the information possible to track
these kind of situations, bugs etc. to help your work.
Now I just can't.
Signing off ;-)
M
Enviado do meu iPhone
No dia 23/04/2014, às 13:02, Matthias Wessendorf <matzew(a)apache.org> escreveu:
> On Wed, Apr 23, 2014 at 1:58 PM, Miguel Lemos <miguel21op(a)gmail.com> wrote:
> No favor. I'm not near a PC..,
>
> As I told before, I've already sent a log related to a similar problem a month
ago, I think.
What Bruno and I tried to say:
We do think that the UNDERLYING problem of this is NOT necessarily the same as it was in
the past.
As said, feel free to send the recent log, if you like
>
> Anyway: this is a recurring problem that deserves a deep attention, I think.
>
> Enviado do meu iPhone
>
> No dia 23/04/2014, às 12:41, "Bruno Oliveira" <bruno(a)abstractj.org>
escreveu:
>
>> Hi Miguel, if you make us a favor and send the logs next time, that would help a
lot.
>>
>> Is hard to guess, because we don't have control over the OpenShift's
infrastructure
>> —
>> abstractj
>>
>>
>>> On Wed, Apr 23, 2014 at 6:42 AM, Miguel Lemos <miguel21op(a)gmail.com>
wrote:
>>> I made a reset to OShift and it's working again.
>>>
>>> This is really an issue that one way or another should be solved...
>>>
>>> Enviado do meu iPhone
>>>
>>> No dia 23/04/2014, às 09:52, Matthias Wessendorf <matzew(a)apache.org>
escreveu:
>>>
>>>> One thing to have in mind:
>>>>
>>>> Openshift does a shutdown of the JBoss AS, after a 48 hours w/ no
traffic.
>>>>
>>>> Than, the next request does boot up the server. In theory that can mean,
a push might be missed, while still booting up the system.
>>>> See ? A metrics/Analytics view would give all that information :-) (e.g.
how many push were sent, and delivered to the 3rd party networks)
>>>>
>>>>
>>>> @Android: is the app running? I think there are issues w/ the Android
process has has been killed
>>>>
>>>>
>>>>
>>>>> On Wed, Apr 23, 2014 at 10:45 AM, Florian Schrofner
<florian.schrofner(a)outlook.com> wrote:
>>>>> I didn't mean that GCM failed.. just thought that GCM maybe
decided to block aerogear now or something like that.
>>>>> But since it happens on iOS too this doesn't seem to be the
matter..
>>>>>
>>>>> Any other clues?
>>>>>
>>>>> _______________________________________________
>>>>> aerogear-dev mailing list
>>>>> aerogear-dev(a)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
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev