Hi, I noticed the same behaviour in my aerogear test server, but I
thought that was something related with openshift. If service is not
used for a while seems like it become suspended until you access again.
I tried to reproduce restarting the server but I couldn't... Just found
something in the logs this morning after 2 days without using it. (At
2:51 I sent the notification)
Log was
-----------------------------
2015/06/13 00:00:00,109 INFO [GCMPushNotificationSender] (EJB default -
2) Deleting ['0'] outdated PushMessageInformation objects
2015/06/13 12:05:30,766 INFO [org.jboss.as.osgi] (MSC service thread
1-5) JBAS011942: Stopping OSGi Framework
2015/06/15 02:51:14,161 INFO [org.jboss.as.configadmin] (ServerService
Thread Pool -- 35) JBAS016200: Activating ConfigAdmin Subsystem
2015/06/15 02:51:14,264 INFO [org.jboss.as.jacorb] (ServerService
Thread Pool -- 41) JBAS016300: Activating JacORB Subsystem
2015/06/15 02:51:14,356 INFO [org.jboss.as.security] (ServerService
Thread Pool -- 58) JBAS013101: Activating Security Subsystem
2015/06/15 02:51:14,258 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 40) JBAS010280: Activating Infinispan
subsystem.
...
...
-------------------------------------
It seem like on saturday 13 service was stopped. And started again on
monday 16 at 2:51 (by my notification???) . I also got this error during
the startup process
--------------------------
2015/06/15 02:51:46,443 INFO
[org.keycloak.adapters.as7.KeycloakAuthenticatorValve] (MSC service
thread 1-5) **** using /WEB-INF/keycloak.json
2015/06/15 02:51:46,760 INFO [JPAPushMessageInformationDao] (EJB
default - 2) Deleting ['2'] outdated PushMessageInformation
objects
2015/06/15 02:51:46,951 INFO
[org.keycloak.services.resources.KeycloakApplication] (MSC service
thread 1-1) Not importing realm aerogear from resource
/WEB-INF/ups-realm.json. It already exists.
2015/06/15 02:51:46,954 INFO [JPAPushMessageInformationDao] (EJB
default - 1) Deleting ['2'] outdated PushMessageInformation
objects
2015/06/15 02:51:46,966 WARN [com.arjuna.ats.arjuna] (EJB default - 1)
ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for
SynchronizationImple< 0:ffff0a21a655:16c5d4f8:557e75e5:f,
org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@d8bbe6
: javax.persistence.OptimisticLockException:
org.hibernate.StaleStateException: Batch update returned unexpected row
count from update [0]; actual row count: 0; expected: 1
at
org.hibernate.ejb.AbstractEntityManagerImpl.wrapStaleStateException(AbstractEntityManagerImpl.java:1402)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1308)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1289)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1295)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.AbstractEntityManagerImpl$CallbackExceptionMapperImpl.mapManagedFlushFailure(AbstractEntityManagerImpl.java:1481)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorImpl.beforeCompletion(SynchronizationCallbackCoordinatorImpl.java:109)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization.beforeCompletion(RegisteredSynchronization.java:53)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
------------------------
Later another generated message at 2:57 was received an processed fine.
I don't know if it's something related with hosting or with UPS. I'm
running 1.0.2 too.
Sorry if this information is not relevant
Alex Ballesté
El 13/06/15 a les 08:01, Matthias Wessendorf ha escrit:
any chance of stack trace?
On Saturday, June 13, 2015, Kelvin Lunsford <kelvin(a)qantel.com
<mailto:kelvin@qantel.com>> wrote:
I restarted Wildfly and I had to log into the UPS console to stop
the registration errors.
The error callback for the plugin push.register() function returns
the message "The server returned the error code 500".
- Kelvin
---------------------------------------------------------------------------
From: aerogear-users-bounces(a)lists.jboss.org <javascript:;>
[mailto:aerogear-users-bounces@lists.jboss.org <javascript:;>] On
Behalf Of Matthias Wessendorf
Sent: Friday, June 12, 2015 12:01 AM
To: aerogear-users(a)lists.jboss.org <javascript:;>
Subject: Re: [Aerogear-users] UPS load on startup
hrm,
that's strange - not noticed so far.
Any details on the error message ? Is that reproducable w/
something like curl ?
On Fri, Jun 12, 2015 at 3:05 AM, Kelvin Lunsford
<kelvin(a)qantel.com <javascript:;>> wrote:
I'm developing a mobile app and testing USP 1.0.2 on Wildfly 8.2.0.
Runs great but I've noticed that when the server is restarted
registration requests from my mobile app fail until I try to
access the ag-push console with a browser and bring up a login
page. Then registration works.
Anyone noticed this?
- Kelvin
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org <javascript:;>
https://lists.jboss.org/mailman/listinfo/aerogear-users
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org <javascript:;>
https://lists.jboss.org/mailman/listinfo/aerogear-users
--
Sent from Gmail Mobile
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
--
Alexandre Ballesté Crevillén alexandre.balleste at udl.cat
====================
Universitat de Lleida
Àrea de sistemes d'Informació i Comunicacions
Analista/Programador
University of Lleida
Information and Communication Systems Service
Tlf: +34 973 702148
Fax: +34 973 702130
=====================
Avís legal/Aviso legal/Avertiment legal/Legal notice
<
http://www.imatge.udl.cat/avis_legal_lopd.html>