May 2016 - Aerogear-users - Jboss List Archives

by Philipp Koetz, mVISE AG

Hello, is there some kind of documentation which endpoints (Google, Android, etc.) are called potentially? We would need this to configure our firewall.

7 years, 11 months

2
4
0 / 0

Variant Updates return 200 but docs say 204

by Luke Holmquist

The variant update endpoint returns a 200 with the updated content, but the docs says it should return a 204 with no Content i've create a JIRA for it, https://issues.jboss.org/browse/AGPUSH-1635 I think PUT's are suppose to be 204's, but there might be things relying on the fact that the update returns data, here is a link to the AndroidVariants update endpoint, https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs...

7 years, 11 months

1
0
0 / 0

Unable to resolve realm public key remotely

by Philipp Koetz, mVISE AG

Hello, i've set up the unified push server and run in this stack trace while trying to access /ag-push/ 2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_72-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_72-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72-internal] Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.8.0_72-internal] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [rt.jar:1.8.0_72-internal] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [rt.jar:1.8.0_72-internal] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [rt.jar:1.8.0_72-internal] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.8.0_72-internal] at java.net.Socket.connect(Socket.java:589) [rt.jar:1.8.0_72-internal] at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) [jsse.jar:1.8.0_72-internal] at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) [httpclient-4.3.6.jar:4.3.6] at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) [httpclient-4.3.6.jar:4.3.6] at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final] ... 14 more SSL setup should be correct, with a self signed cert, till accessing the wildfly start page via https works correctly. If it helps I can also provide the standalone-full.xml. I'm using version 1.13 on Wildfly 8.2.1. The error appears on http and https. Regards, Philipp Koetz

7 years, 11 months

3
5
0 / 0

UPS/Keycloak Decouple status?

by Luke Holmquist

Hey peeps. while i was doing some work on the node admin client i just cretated, i was think about this $SUBJECT and saw that the PR is still open, https://github.com/aerogear/aerogear-unifiedpush-server/pull/677 I know abstractj did some awesome work around this, but i wasn't sure what the status was. i see it's been open for a while. -Luke

7 years, 11 months

2
1
0 / 0

Message posted through RestAPI does not show up as JSON in Android

by vvalluru

We are using Unified Push server 1.1.0 final We created a format for message, which we want to post to our Android and iOS users. Message has some userData. On iOS, data shows up fine as a proper JSON, however, for android, the data shows as a string. Any Suggestions would be very helpful. Thanks Vish The message submitted is submitted like this: { "message": { "alert" : "Remote service failed. View FAQ's.", "sound": "default", "badge": -1, "user-data": { "SXM": { "CATEGORY" : "SERVICE", "SERVICETYPE": "Remote", "SRID": "BB4FC7F0-15E9-11E6-9F41-0050569C3256", "APPCONTENT": "UNKNOWN", "STATUS": "FAIL", "STATUSCHANGE_DATETIME": "UNKNOWN", "URL": "XYZABC.com"}}, "apns": {"action-category": "Service"}}, criteria: {"alias": ["A337544939901E078A3C7DF1435DFD0B"]} } Android receives message like this: {aerogear-push-id=4d8ea259-ad94-49f0-b470-50fc4bcf3a20, SXM={CATEGORY=SERVICE, SERVICETYPE=Remote, SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, APPCONTENT=UNKNOWN, STATUS=FAIL, STATUSCHANGE_DATETIME=UNKNOWN, URL=XYZABC.com }, alert=Remote service failed. View FAQ's., badge=-1, sound=default, collapse_key=do_not_collapse } If we remove the SXM tag under userData, issue remains the same: Android receives message like this: {aerogear-push-id=4d8ea259-ad94-49f0-b470-50fc4bcf3a20, CATEGORY=SERVICE, SERVICETYPE=Remote, SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, APPCONTENT=UNKNOWN, STATUS=FAIL, STATUSCHANGE_DATETIME=UNKNOWN, URL=XYZABC.com, alert=Remote service failed. View FAQ's., collapse_key=do_not_collapse } -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Message-posted-through-RestAP... Sent from the aerogear-users mailing list archive at Nabble.com.

7 years, 11 months

1
0
0 / 0

admin REST client for node

by Luke Holmquist

https://www.npmjs.com/package/unifiedpush-admin-client I remember a little while back someone created an admin client in Java, so i decided to start one in node.js ATM for the 0.1.0 release, i've only implemented the CRUD for applications, following these docs https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#838429674 The only thing i need to do to get "authenitcated" with keycloak was to switch direct access grants to on in the "unifiedpush-server-js" client. it also assumes that you are using the coupled KC/UPS bundle. which i think is the only way right now. once they become decoupled, then i can modify the client accordingly. The tests are currently just mocking what the ups would return. I would like to get some integration tests setup, but i'm not to sure how to automate the "turning on" of the direct access grants. i could probably use docker for the sever setup anyway, here it is :) and more functionality to come -Luke

7 years, 11 months

1
0
0 / 0

Handshake issue when connecting to APNS (from OpenShift Online)

by Florian Traverse

Hi all :) We encounter an issue since yesterday on our aerogear server running in production for several months on OpenShift Online ( OPENSHIFT_AEROGEAR_PUSH_VERSION=1.0.3 ) : Management interface would report the handshake error as well, and none of all our iOS pushes, whatever the `application`, whatever the `variant`, would work. We're looking for what can go wrong in order to fix it. We still have both RAM and disk available, and a `gear restart` would not help in the matter. Here's what the stacktrace looks like in the logs, can anybody help ? ``` ERROR [com.notnoop.apns.internal.ApnsConnectionImpl] (EJB default - 4) Couldn't send message after 3 retries.Message(Id=1; Token=<TOKEN>; Payload={"<some_payload_property>":"<some numeric value>","aps":{"alert":"<The notification text>","badge":-1}}): javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) [jsse.jar:1.7.0_85] at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1916) [jsse.jar:1.7.0_85] at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:279) [jsse.jar:1.7.0_85] at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:273) [jsse.jar:1.7.0_85] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1469) [jsse.jar:1.7.0_85] at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:213) [jsse.jar:1.7.0_85] at sun.security.ssl.Handshaker.processLoop(Handshaker.java:913) [jsse.jar:1.7.0_85] at sun.security.ssl.Handshaker.process_record(Handshaker.java:849) [jsse.jar:1.7.0_85] at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1035) [jsse.jar:1.7.0_85] at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1344) [jsse.jar:1.7.0_85] at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:721) [jsse.jar:1.7.0_85] at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:122) [jsse.jar:1.7.0_85] at java.io.OutputStream.write(OutputStream.java:75) [rt.jar:1.7.0_85] at com.notnoop.apns.internal.ApnsConnectionImpl.sendMessage(ApnsConnectionImpl.java:322) [apns-1.0.0.Beta5.jar:] at com.notnoop.apns.internal.ApnsConnectionImpl.sendMessage(ApnsConnectionImpl.java:310) [apns-1.0.0.Beta5.jar:] at com.notnoop.apns.internal.ApnsServiceImpl.push(ApnsServiceImpl.java:46) [apns-1.0.0.Beta5.jar:] at com.notnoop.apns.internal.AbstractApnsService.push(AbstractApnsService.java:102) [apns-1.0.0.Beta5.jar:] at com.notnoop.apns.internal.ApnsServiceImpl.push(ApnsServiceImpl.java:36) [apns-1.0.0.Beta5.jar:] at org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender.sendPushMessage(APNsPushNotificationSender.java:109) [unifiedpush-push-1.0.3.jar:1.0.3] at org.jboss.aerogear.unifiedpush.message.SenderServiceImpl.send(SenderServiceImpl.java:116) [unifiedpush-push-1.0.3.jar:1.0.3] at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source) [:1.7.0_85] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_85] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_85] at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) [wildfly-weld-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) [wildfly-weld-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:407) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:55) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) [wildfly-weld-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.NonPooledEJBComponentInstanceAssociatingInterceptor.processInvocation(NonPooledEJBComponentInstanceAssociatingInterceptor.java:59) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:273) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:340) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:95) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:448) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:185) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:182) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.LogDiagnosticContextRecoveryInterceptor.processInvocation(LogDiagnosticContextRecoveryInterceptor.java:79) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) at org.jboss.as.ejb3.component.interceptors.AsyncFutureInterceptorFactory$1$2.runInvocation(AsyncFutureInterceptorFactory.java:97) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:73) [wildfly-ejb3-8.1.0.Final.jar:8.1.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_85] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_85] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_85] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: sun.security.validator.ValidatorException: No trusted certificate found at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:394) [rt.jar:1.7.0_85] at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:134) [rt.jar:1.7.0_85] at sun.security.validator.Validator.validate(Validator.java:260) [rt.jar:1.7.0_85] at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326) [jsse.jar:1.7.0_85] at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231) [jsse.jar:1.7.0_85] at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126) [jsse.jar:1.7.0_85] at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1451) [jsse.jar:1.7.0_85] ... 87 more 2015-11-05 04:32:39,596 WARNING [APNsPushNotificationSender] (EJB default - 4) Error on 'ios' delivery 2015-11-05 04:40:00,169 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-26) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:21,553 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-30) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:26,675 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-33) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:28,864 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-34) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:30,969 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-37) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:33,150 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-36) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:36,375 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-39) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:43,324 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-43) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:46,273 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-41) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:48,448 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-40) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:50,514 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-42) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:52,733 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-45) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:55,093 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-46) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:56,742 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-44) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:40:58,947 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-51) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:41:01,469 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-50) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:41:03,297 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-52) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! 2015-11-05 04:41:09,376 WARN [org.hibernate.hql.internal.ast.QueryTranslatorImpl] (default task-55) HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! -- Florian TRAVERSE Software Architect Allocab, votre chauffeur sur-mesure M. +33 6 12 39 66 50 A. 7 impasse Charles Petit, 75011 Paris W. www.allocab.com E. florian.traverse(a)allocab.com

7 years, 11 months

5
11
0 / 0

Push message don't send

by oliver

Aerogear don't send message to networks (apn/gcm), server is on openshift with a non free account. Also any recomendation for memory and cpu?, thank you in advance. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Push-message-don-t-send-tp630... Sent from the aerogear-users mailing list archive at Nabble.com.

7 years, 11 months

3
3
0 / 0

deploy failure for Master

by Luke Holmquist

so i'm trying to deploy what is currently on master to wildfly 9(also tried 10) and i'm getting this error: https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc i've copied the h2 db deployment script to the wildly deployment directory, manually copied the auth-server and ag-push war files to the wildlfy deployment directory from their respective target directories, started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0" perhaps i'm missing a step?

7 years, 11 months

2
3
0 / 0

JBoss Unified Push - iOS registers but does not receive notifications

by Walto, David

I have a JBoss Unified Push account with Android and iOS variants. The Android works fine, the device registers and receives notifications. On my iOS variant, when I start my app the device registers and I can see it as an installation on the Unified Push applications page. But when I Send a Push, the device never gets the notification, and the installation goes away. I would think the registration of the device being removed would be a clue on the issue. Can you spread some light on what might be causing this. Thanks David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology ---------------------------------------------------------------------- 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.

7 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Aerogear-users May 2016