Push Problem on 1.1.1.Final Push
by Javornik, Romain
Hello,
We are currently running Aerogear Push 1.1.1.Final on a Jboss EAP 6.4 since a year now without any issues.
However, a problem that we had prior 1.1.0 release (http://lists.jboss.org/pipermail/aerogear-users/2016-June/000821.html) is coming back.
When we are making a push we got this error (sometimes) :
08:29:08,265 WARNING [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Internal cache size exceeded, new size is: 150
08:29:08,265 SEVERE [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Error sending payload to APNs server: com.notnoop.exceptions.ApnsDeliveryErrorException: Failed to deliver notification with error code 8
at com.notnoop.apns.internal.ApnsConnectionImpl$2.run(ApnsConnectionImpl.java:199) [apns-1.0.0.Beta6.jar:]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
Do you know where the problem might come from ?
Best Regards,
Romain Javornik
6 years, 11 months
AeroGear Android Offline
by Daniel Passos
A long time ago we try to draft an offline library, we have created an
aerogear-android-offline GH repo, but we did not work too much on it there
and never released it.
Should we delete this repo or only add a notice on the README
--
-- Passos
7 years
A question about unifiedpush crashed tables
by Federico Cerminara
Hi,
we are recognizing internally a strange behaviour with push notifications.
Aerogear server seems to be no more reachable and looking in jboss
(wildfly) logs for some explanations, we founds some ups database table are
crashed and "need" to be repaired.
Have you ever experienced this scenario and eventually could you suggest me
an approach to solve it? Googling about the error messages, someone suggest
to repair tables using a specific command; otherwise i could drop the
crashed tabled and creating them using the sql creation code from another
running installation of unified push database. Crashed tables seem to be
variant_metric_info and push_message_info.
Thanks anyway for your important support and for the time you'll spend
reading this mail.
Federico.
08:51:26,167 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB
default - 1) SQL Error: 126, SQLState: HY000
08:51:26,214 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB
default - 1) Incorrect key file for table
'.\unifiedpush\variant_metric_info.MYI'; try to repair it
08:51:26,230 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB
default - 1) Table 'variant_metric_info' is marked as crashed and should be
repaired
Caused by: java.sql.SQLException: Incorrect key file for table
'.\unifiedpush\variant_metric_info.MYI'; try to repair it
Here about reparing tables:
https://stackoverflow.com/questions/4357270/table-is-marked-as-crashed-an...
7 years
