From ya at sherpa-solutions.com Thu Sep 1 10:57:26 2016 From: ya at sherpa-solutions.com (Yoann Archambault) Date: Thu, 1 Sep 2016 10:57:26 -0400 Subject: [Aerogear-users] All requests to server are hanging, never completing Message-ID: Hello, Our deployment of Aerogear in production has stopped responding to requests on the ag-push.war or auth.war applications (wildfly admin console works fine). I can only see one type of stack trace when i do a kill -3 (see bellow). So far i've tried restarting wildfly, undeploying/deploying both WARs, rebooting the server and nothing has had any effect. There has been no change in configuration or code for a few weeks now and i've had a couple of service restarts without a issue. I'm using UPS 1.1.3-final on a CentOS server. Also i'm not sure if its relevant but since the start we've been using a slightly modified version of UPS which we built with maven. The only change is using the push_message_info.client_identifier for our own purpose. Its basically a one line code change. "default task-62" #221 prio=5 os_prio=0 tid=0x00007fc7901a9000 nid=0x32c4 runnable [0x00007fc6eb7f5000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:170) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973) - locked <0x00000006c5abff60> (a java.lang.Object) at sun.security.ssl.SSLSocketImpl.readDataRecord( SSLSocketImpl.java:930) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) - locked <0x00000006c5ac0020> (a sun.security.ssl.AppInputStream) at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer( AbstractSessionInputBuffer.java:160) at org.apache.http.impl.io.SocketInputBuffer.fillBuffer( SocketInputBuffer.java:84) at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine( AbstractSessionInputBuffer.java:273) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead( DefaultHttpResponseParser.java:140) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead( DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse( AbstractMessageParser.java:260) at org.apache.http.impl.AbstractHttpClientConnection. receiveResponseHeader(AbstractHttpClientConnection.java:283) at org.apache.http.impl.conn.DefaultClientConnection. receiveResponseHeader(DefaultClientConnection.java:251) at org.apache.http.impl.conn.AbstractClientConnAdapter. receiveResponseHeader(AbstractClientConnAdapter.java:223) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse( HttpRequestExecutor.java:271) at org.apache.http.protocol.HttpRequestExecutor.execute( HttpRequestExecutor.java:123) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute( DefaultRequestDirector.java:685) at org.apache.http.impl.client.DefaultRequestDirector.execute( DefaultRequestDirector.java:487) at org.apache.http.impl.client.AbstractHttpClient.doExecute( AbstractHttpClient.java:863) at org.apache.http.impl.client.CloseableHttpClient.execute( CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute( CloseableHttpClient.java:106) at org.apache.http.impl.client.CloseableHttpClient.execute( CloseableHttpClient.java:57) at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey( AdapterDeploymentContext.java:105) at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment( AdapterDeploymentContext.java:83) at org.keycloak.adapters.PreAuthActionsHandler.preflightCors( PreAuthActionsHandler.java:71) at org.keycloak.adapters.PreAuthActionsHandler.handleRequest( PreAuthActionsHandler.java:47) at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler. handleRequest(ServletPreAuthActionsHandler.java:68) at io.undertow.server.handlers.PredicateHandler.handleRequest( PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler. handleFirstRequest(ServletInitialHandler.java:282) at io.undertow.servlet.handlers.ServletInitialHandler. dispatchRequest(ServletInitialHandler.java:261) at io.undertow.servlet.handlers.ServletInitialHandler.access$ 000(ServletInitialHandler.java:80) at io.undertow.servlet.handlers.ServletInitialHandler$1. handleRequest(ServletInitialHandler.java:172) at io.undertow.server.Connectors.executeRootHandler(Connectors. java:199) at io.undertow.server.HttpServerExchange$1.run( HttpServerExchange.java:774) at java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run( ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) I've been trying to solve this for 2 days without success, so at this point any help would be greatly appreciated! -- Yoann -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160901/dc4e0c51/attachment-0001.html From jesus90martin at gmail.com Mon Sep 5 09:28:43 2016 From: jesus90martin at gmail.com (=?UTF-8?B?SmVzw7pzIE1hcnTDrW4gR29uesOhbGV6?=) Date: Mon, 5 Sep 2016 15:28:43 +0200 Subject: [Aerogear-users] Using aerogear-cordova-push 3.0.0 - Success callback fires only once in IOS Message-ID: Hello, I am using aerogear-cordova-push 3.0.0 in my cordova app, everything work fine in android but in iOS the success callback fires only once, for example if i try to change categories, them change but succces callback is not invoked. I have seen that in AGCORDOVA-125 you resolved it for Android https://issues.jboss.org/browse/AGCORDOVA-125 Can you help me, to solve it on iOS? I think it is an important bug. Its easy to reproduce, just call push.register two times, the first will work and the second wont (Working with of iOS-4.2.1 and cordova 6.2.0) Thank you in advance! -- Jes?s Mart?n Gonzalez Tel: +34 654420529 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160905/7c0246c1/attachment.html From supittma at redhat.com Wed Sep 7 15:37:58 2016 From: supittma at redhat.com (Summers Pittman) Date: Wed, 7 Sep 2016 15:37:58 -0400 Subject: [Aerogear-users] All requests to server are hanging, never completing In-Reply-To: References: Message-ID: What version of the JDK are you running Wildfly on? A quick Googling of some of the issues in your stack trace point to this thread ( https://github.com/notnoop/java-apns/issues/116) which claims a similar issue is a JVM bug. It sounds like you might be hitting a (similar) race condition. A few things that come to mind to check: Do you notice if the server is using a lot of CPU or memory? Are you possibly out of disk space? Do your system logs have anything interesting which might shed some light on the issue? Is selinux blocking something? Sorry you are having troubles, Summers On Thu, Sep 1, 2016 at 10:57 AM, Yoann Archambault wrote: > Hello, > > Our deployment of Aerogear in production has stopped responding to > requests on the ag-push.war or auth.war applications (wildfly admin console > works fine). I can only see one type of stack trace when i do a kill -3 > (see bellow). So far i've tried restarting wildfly, undeploying/deploying > both WARs, rebooting the server and nothing has had any effect. There has > been no change in configuration or code for a few weeks now and i've had a > couple of service restarts without a issue. I'm using UPS 1.1.3-final on a > CentOS server. > > Also i'm not sure if its relevant but since the start we've been using a > slightly modified version of UPS which we built with maven. The only change > is using the push_message_info.client_identifier for our own purpose. Its > basically a one line code change. > > "default task-62" #221 prio=5 os_prio=0 tid=0x00007fc7901a9000 nid=0x32c4 > runnable [0x00007fc6eb7f5000] > java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java > :116) > at java.net.SocketInputStream.read(SocketInputStream.java:170) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) > at sun.security.ssl.InputRecord.read(InputRecord.java:503) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl. > java:973) > - locked <0x00000006c5abff60> (a java.lang.Object) > at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl. > java:930) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) > - locked <0x00000006c5ac0020> (a sun.security.ssl.AppInputStream) > at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffe > r(AbstractSessionInputBuffer.java:160) > at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketI > nputBuffer.java:84) > at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine( > AbstractSessionInputBuffer.java:273) > at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHea > d(DefaultHttpResponseParser.java:140) > at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHea > d(DefaultHttpResponseParser.java:57) > at org.apache.http.impl.io.AbstractMessageParser.parse(Abstract > MessageParser.java:260) > at org.apache.http.impl.AbstractHttpClientConnection.receiveRes > ponseHeader(AbstractHttpClientConnection.java:283) > at org.apache.http.impl.conn.DefaultClientConnection.receiveRes > ponseHeader(DefaultClientConnection.java:251) > at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveR > esponseHeader(AbstractClientConnAdapter.java:223) > at org.apache.http.protocol.HttpRequestExecutor.doReceiveRespon > se(HttpRequestExecutor.java:271) > at org.apache.http.protocol.HttpRequestExecutor.execute(HttpReq > uestExecutor.java:123) > at org.apache.http.impl.client.DefaultRequestDirector.tryExecut > e(DefaultRequestDirector.java:685) > at org.apache.http.impl.client.DefaultRequestDirector.execute(D > efaultRequestDirector.java:487) > at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs > tractHttpClient.java:863) > at org.apache.http.impl.client.CloseableHttpClient.execute(Clos > eableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(Clos > eableHttpClient.java:106) > at org.apache.http.impl.client.CloseableHttpClient.execute(Clos > eableHttpClient.java:57) > at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmK > ey(AdapterDeploymentContext.java:105) > at org.keycloak.adapters.AdapterDeploymentContext.resolveDeploy > ment(AdapterDeploymentContext.java:83) > at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(Pr > eAuthActionsHandler.java:71) > at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(Pr > eAuthActionsHandler.java:47) > at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler. > handleRequest(ServletPreAuthActionsHandler.java:68) > at io.undertow.server.handlers.PredicateHandler.handleRequest(P > redicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFir > stRequest(ServletInitialHandler.java:282) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchR > equest(ServletInitialHandler.java:261) > at io.undertow.servlet.handlers.ServletInitialHandler.access$00 > 0(ServletInitialHandler.java:80) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleR > equest(ServletInitialHandler.java:172) > at io.undertow.server.Connectors.executeRootHandler(Connectors. > java:199) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchan > ge.java:774) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool > Executor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo > lExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > > I've been trying to solve this for 2 days without success, so at this > point any help would be greatly appreciated! > > -- > Yoann > > _______________________________________________ > 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/20160907/2a70862a/attachment.html From divya.sree at hp.com Thu Sep 8 03:11:05 2016 From: divya.sree at hp.com (Sree, Divya (TCS S&CO Platform Team (L2/L3))) Date: Thu, 8 Sep 2016 07:11:05 +0000 Subject: [Aerogear-users] FW: Aerogear Plugin issue - Notification opened metric In-Reply-To: References: Message-ID: Hi Team, Is there any fix provided for below use case #2? Thanks, Divya From: Prasad, Ganesh Sent: Thursday, July 28, 2016 9:55 PM To: aerogear-users at lists.jboss.org Cc: Bhatt, Rohit (PPSIT); Sree, Divya Subject: Aerogear Plugin issue - Notification opened metric Hello We were testing the usage of notification opened metric and our application is Cordova based pushConfig: { 'pushServerURL': 'url', 'alias': 'app name', 'sendMetricInfo': 'true', Below are the observation 1. Clicking on the push notification while the app is in the background increments the opened count 2. If the app is completely shut down, on receiving push notification : * Clicking on the push notification starts the app but does not increment the opened count Is there any fix available for #2 ? Thanks ganesh -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160908/d82c9f14/attachment-0001.html From matzew at apache.org Thu Sep 8 03:48:06 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 8 Sep 2016 09:48:06 +0200 Subject: [Aerogear-users] FW: Aerogear Plugin issue - Notification opened metric In-Reply-To: References: Message-ID: Hello, Divya, we haven't been able to look into that yet. However, looks like on the JIRA I created to capture your issue, there was a proposal: https://issues.jboss.org/browse/AGCORDOVA-158 If you want to try that, and in case it works, you could sent in a PR, which we could than immediately merge :-) Greetings, Matthias On Thu, Sep 8, 2016 at 9:11 AM, Sree, Divya (TCS S&CO Platform Team (L2/L3)) wrote: > Hi Team, > > > > Is there any fix provided for below *use case #2*? > > > > Thanks, > > Divya > > > > *From:* Prasad, Ganesh > *Sent:* Thursday, July 28, 2016 9:55 PM > *To:* aerogear-users at lists.jboss.org > *Cc:* Bhatt, Rohit (PPSIT); Sree, Divya > *Subject:* Aerogear Plugin issue - Notification opened metric > > > > Hello > > > > We were testing the usage of notification opened metric and our > application is Cordova based > > > > pushConfig: { > > 'pushServerURL': 'url', > > 'alias': 'app name', > > 'sendMetricInfo': ?true?, > > > > > > Below are the observation > > > > 1. Clicking on the push notification while the app is in the > background increments the opened count > > *2. **If the app is completely shut down, on receiving push > notification :* > > ? *Clicking on the push notification starts the app but does not > increment the opened count* > > > > Is there any fix available for #2 ? > > > > Thanks > > ganesh > > _______________________________________________ > 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/20160908/0dba5429/attachment.html From scm.blanc at gmail.com Fri Sep 9 07:05:59 2016 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 9 Sep 2016 13:05:59 +0200 Subject: [Aerogear-users] [RELEASE] Unifiedpush 1.2.0-alpha.2 Message-ID: Hi Folks, I'm happy to announce that the UPS 1.2.0-alpha.2 release has been staged. It's available here : https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-8977 Test and have fun ... I should be pushed next mid-week (along with docker image updates) Sebi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160909/61e2c229/attachment.html From edewit at redhat.com Fri Sep 9 07:43:02 2016 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 9 Sep 2016 13:43:02 +0200 Subject: [Aerogear-users] aerogear-cordova-push 3.0.1 Message-ID: Hi, We fixed a couple of bug on aerogear-cordova-push and would like to release it. The 3.0.x branch is ready for testing -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160909/6c9f93af/attachment.html From kelvin at qantel.com Fri Sep 9 16:40:12 2016 From: kelvin at qantel.com (Kelvin Lunsford) Date: Fri, 9 Sep 2016 20:40:12 +0000 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> Message-ID: <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> My categories no longer work on android because I use ":" characters in my category names. Last May aerogear-android-push:3.0.0 was released with Topics and now the android plugin refuses to accept my category names with non-Topic compatible characters. IOS still works with non-Topic compatible characters, but there is a regression in android. I warned you. Category names should have been percent encoded before applying them to the Topic interfaces in the plugin and UPS. It would have prevented the regression, but nobody did it. Now notifications are broken on the android version of my app. If I want to make it work with the current plugin I will have to change my category names to avoid using non-topic compatible characters. If I make the change it will affect my android and IOS mobile apps, and I will have to change the system that posts the notification requests to UPS so it also changes the names. If no one responds with a "No, wait, we'll fix it!" that is what I will do. - Kelvin From: Kelvin Lunsford Sent: Tuesday, August 18, 2015 3:25 PM To: 'aerogear-users at lists.jboss.org' Subject: RE: [Aerogear-users] categories have been hijacked You need topic compliant percent encoding/decoding functions to use on category names when setting them to/from topic names. You can encode by using the android.net.Uri.encode() function and replacing the characters missed by the encode() function. Uri.decode() will work as is. Equivalent encoding would have to be done in java for UPS when it accesses a topic. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 18, 2015 6:26 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: Summers, What happens if a category name is not GCM topic compatible? That is a good question. Currently you will get a error because it fails validation. We've created a JIRA to track this issue here : https://issues.jboss.org/browse/AGPUSH-1501 Keep the hits coming. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 11, 2015 10:03 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Kelvin, For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: Hi Summers, GCM topic messages go to all devices registered for the topic. Topic notifications cannot be restricted to an alias or list of aliases. The way it worked before, and still works on ios, you can send a command to UPS with an "alias" name AND a "categories" name and it will only go to devices that have registered using that "alias" name AND that "categories" name. UPS finds which devices meet the selection criteria and push notification requests are sent for those devices. Requests with aliases and categories can target specific users in a group. With real "categories" you can segment users into groups, so every device can be assigned a category, and sub-groups can be defined by using more than one category per device. This is useful for geographic or organizational targeting. I have no problem with GCM topics. Just make it a new feature. Give me back my categories. So the goal isn't to replace or hijack categories with topics. The goal is to leverage Google's API fully and transparently to the UPS user so that we make fewer calls and provide a better experience. You have some great use cases that haven't been brought up. Keep in mind that the PRs open right now are a "first draft" of the technology. Feel free to join in on the discussion about topics on aerogear-dev. It is really important we do this right and I think you can help with that. Summers - Kelvin --------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Monday, August 10, 2015 6:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: >Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. > >For version 2.0.2 "categories" only works for ios. > >It looks like "categories" is being hijacked in android for a GCM feature called "topics". > >I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing. What do categories do that topics do not do? >New features should get new names and new commands. > >- Kelvin _______________________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160909/694568b6/attachment-0001.html From matzew at apache.org Mon Sep 12 03:33:16 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 12 Sep 2016 09:33:16 +0200 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> Message-ID: Hello, sorry for the problems you are encountering with our UPS and its client side libraries. I've created a JIRA ticket to capture the problem: https://issues.jboss.org/browse/AGDROID-565 greetings, Matthias On Fri, Sep 9, 2016 at 10:40 PM, Kelvin Lunsford wrote: > My categories no longer work on android because I use ":" characters in my > category names. > > > > Last May aerogear-android-push:3.0.0 was released with Topics and now the > android plugin refuses to accept my category names with non-Topic > compatible characters. > > > > IOS still works with non-Topic compatible characters, but there is a > regression in android. > > > > I warned you. Category names should have been percent encoded before > applying them to the Topic interfaces in the plugin and UPS. It would have > prevented the regression, but nobody did it. > > > > Now notifications are broken on the android version of my app. > > > > If I want to make it work with the current plugin I will have to change my > category names to avoid using non-topic compatible characters. If I make > the change it will affect my android and IOS mobile apps, and I will have > to change the system that posts the notification requests to UPS so it also > changes the names. > > > > If no one responds with a "No, wait, we'll fix it!" that is what I will do. > > > > - Kelvin > > > > > > *From:* Kelvin Lunsford > *Sent:* Tuesday, August 18, 2015 3:25 PM > *To:* 'aerogear-users at lists.jboss.org' > *Subject:* RE: [Aerogear-users] categories have been hijacked > > > > You need topic compliant percent encoding/decoding functions to use on > category names when setting them to/from topic names. > > > > You can encode by using the android.net.Uri.encode() function and > replacing the characters missed by the encode() function. Uri.decode() > will work as is. > > > > Equivalent encoding would have to be done in java for UPS when it accesses > a topic. > > > > - Kelvin > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org ] *On > Behalf Of *Summers Pittman > *Sent:* Tuesday, August 18, 2015 6:26 AM > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > > > > > On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: > > Summers, > > > > What happens if a category name is not GCM topic compatible? > > That is a good question. Currently you will get a error because it fails > validation. We've created a JIRA to track this issue here : > https://issues.jboss.org/browse/AGPUSH-1501 > > > > Keep the hits coming. > > > > - Kelvin > > > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Summers Pittman > *Sent:* Tuesday, August 11, 2015 10:03 AM > > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > Kelvin, > > > > For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 > > > > On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: > > > > > > On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: > > Hi Summers, > > GCM topic messages go to all devices registered for the topic. Topic > notifications cannot be restricted to an alias or list of aliases. > > The way it worked before, and still works on ios, you can send a command > to UPS with an "alias" name AND a "categories" name and it will only go to > devices that have registered using that "alias" name AND that "categories" > name. UPS finds which devices meet the selection criteria and push > notification requests are sent for those devices. > > Requests with aliases and categories can target specific users in a group. > > With real "categories" you can segment users into groups, so every device > can be assigned a category, and sub-groups can be defined by using more > than one category per device. This is useful for geographic or > organizational targeting. > > I have no problem with GCM topics. Just make it a new feature. Give me > back my categories. > > > > So the goal isn't to replace or hijack categories with topics. The goal is > to leverage Google's API fully and transparently to the UPS user so that we > make fewer calls and provide a better experience. You have some great use > cases that haven't been brought up. Keep in mind that the PRs open right > now are a "first draft" of the technology. Feel free to join in on the > discussion about topics on aerogear-dev. It is really important we do this > right and I think you can help with that. > > > > Summers > > > > > - Kelvin > > > ------------------------------------------------------------ > --------------------------- > From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] On Behalf Of Summers Pittman > Sent: Monday, August 10, 2015 6:12 PM > To: aerogear-users at lists.jboss.org > Subject: Re: [Aerogear-users] categories have been hijacked > > > > > > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: > >Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > > >For version 2.0.2 "categories" only works for ios. > > > >It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > > >I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > > What do categories do that topics do not do? > > >New features should get new names and new commands. > > > >- Kelvin > > > _______________________________________________ > 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 > > > > _______________________________________________ > 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/20160912/949511bf/attachment.html From matzew at apache.org Mon Sep 12 03:46:25 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 12 Sep 2016 09:46:25 +0200 Subject: [Aerogear-users] [aerogear-dev] [RELEASE] Unifiedpush 1.2.0-alpha.2 In-Reply-To: References: Message-ID: On this tag, we need the signed artifacts: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.2.0-alpha.2 On Fri, Sep 9, 2016 at 1:05 PM, Sebastien Blanc wrote: > Hi Folks, > > I'm happy to announce that the UPS 1.2.0-alpha.2 release has been staged. > > It's available here : > > https://repository.jboss.org/nexus/content/repositories/ > jboss_releases_staging_profile-8977 > > Test and have fun ... > > I should be pushed next mid-week (along with docker image updates) > > Sebi > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- 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/20160912/fa1a58f1/attachment-0001.html From matzew at apache.org Mon Sep 12 03:56:03 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 12 Sep 2016 09:56:03 +0200 Subject: [Aerogear-users] [aerogear-dev] [RELEASE] Unifiedpush 1.2.0-alpha.2 In-Reply-To: References: Message-ID: Besides that, I've tested the release (via docker), and it works fine +1 on releasing this On Mon, Sep 12, 2016 at 9:46 AM, Matthias Wessendorf wrote: > On this tag, we need the signed artifacts: > https://github.com/aerogear/aerogear-unifiedpush-server/ > releases/tag/1.2.0-alpha.2 > > > > On Fri, Sep 9, 2016 at 1:05 PM, Sebastien Blanc > wrote: > >> Hi Folks, >> >> I'm happy to announce that the UPS 1.2.0-alpha.2 release has been staged. >> >> It's available here : >> >> https://repository.jboss.org/nexus/content/repositories/jbos >> s_releases_staging_profile-8977 >> >> Test and have fun ... >> >> I should be pushed next mid-week (along with docker image updates) >> >> Sebi >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > 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/20160912/ba0e0584/attachment.html From dpassos at redhat.com Mon Sep 12 12:09:56 2016 From: dpassos at redhat.com (Daniel Passos) Date: Mon, 12 Sep 2016 13:09:56 -0300 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> Message-ID: Hey Kelvin, It's a knowledge[1] bug fixed[2] in AeroGear Android Store cause by a GSON bug[3]. I'm going to create a new version of AeroGear Android Push library using the new Store version to fix this bug. [1] https://issues.jboss.org/browse/AGDROID-564 [2] https://github.com/aerogear/aerogear-android-store/pull/41 [3] https://github.com/google/gson/issues/210 On Mon, Sep 12, 2016 at 4:33 AM, Matthias Wessendorf wrote: > Hello, > > sorry for the problems you are encountering with our UPS and its client > side libraries. I've created a JIRA ticket to capture the problem: > https://issues.jboss.org/browse/AGDROID-565 > > greetings, > Matthias > > On Fri, Sep 9, 2016 at 10:40 PM, Kelvin Lunsford > wrote: > >> My categories no longer work on android because I use ":" characters in >> my category names. >> >> >> >> Last May aerogear-android-push:3.0.0 was released with Topics and now the >> android plugin refuses to accept my category names with non-Topic >> compatible characters. >> >> >> >> IOS still works with non-Topic compatible characters, but there is a >> regression in android. >> >> >> >> I warned you. Category names should have been percent encoded before >> applying them to the Topic interfaces in the plugin and UPS. It would have >> prevented the regression, but nobody did it. >> >> >> >> Now notifications are broken on the android version of my app. >> >> >> >> If I want to make it work with the current plugin I will have to change >> my category names to avoid using non-topic compatible characters. If I >> make the change it will affect my android and IOS mobile apps, and I will >> have to change the system that posts the notification requests to UPS so it >> also changes the names. >> >> >> >> If no one responds with a "No, wait, we'll fix it!" that is what I will >> do. >> >> >> >> - Kelvin >> >> >> >> >> >> *From:* Kelvin Lunsford >> *Sent:* Tuesday, August 18, 2015 3:25 PM >> *To:* 'aerogear-users at lists.jboss.org' >> *Subject:* RE: [Aerogear-users] categories have been hijacked >> >> >> >> You need topic compliant percent encoding/decoding functions to use on >> category names when setting them to/from topic names. >> >> >> >> You can encode by using the android.net.Uri.encode() function and >> replacing the characters missed by the encode() function. Uri.decode() >> will work as is. >> >> >> >> Equivalent encoding would have to be done in java for UPS when it >> accesses a topic. >> >> >> >> - Kelvin >> >> >> >> *From:* aerogear-users-bounces at lists.jboss.org [ >> mailto:aerogear-users-bounces at lists.jboss.org >> ] *On Behalf Of *Summers Pittman >> *Sent:* Tuesday, August 18, 2015 6:26 AM >> *To:* aerogear-users at lists.jboss.org >> *Subject:* Re: [Aerogear-users] categories have been hijacked >> >> >> >> >> >> >> >> On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford >> wrote: >> >> Summers, >> >> >> >> What happens if a category name is not GCM topic compatible? >> >> That is a good question. Currently you will get a error because it fails >> validation. We've created a JIRA to track this issue here : >> https://issues.jboss.org/browse/AGPUSH-1501 >> >> >> >> Keep the hits coming. >> >> >> >> - Kelvin >> >> >> >> >> >> >> >> *From:* aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] *On Behalf Of *Summers Pittman >> *Sent:* Tuesday, August 11, 2015 10:03 AM >> >> >> *To:* aerogear-users at lists.jboss.org >> *Subject:* Re: [Aerogear-users] categories have been hijacked >> >> >> >> Kelvin, >> >> >> >> For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 >> >> >> >> On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman >> wrote: >> >> >> >> >> >> On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford >> wrote: >> >> Hi Summers, >> >> GCM topic messages go to all devices registered for the topic. Topic >> notifications cannot be restricted to an alias or list of aliases. >> >> The way it worked before, and still works on ios, you can send a command >> to UPS with an "alias" name AND a "categories" name and it will only go to >> devices that have registered using that "alias" name AND that "categories" >> name. UPS finds which devices meet the selection criteria and push >> notification requests are sent for those devices. >> >> Requests with aliases and categories can target specific users in a group. >> >> With real "categories" you can segment users into groups, so every device >> can be assigned a category, and sub-groups can be defined by using more >> than one category per device. This is useful for geographic or >> organizational targeting. >> >> I have no problem with GCM topics. Just make it a new feature. Give me >> back my categories. >> >> >> >> So the goal isn't to replace or hijack categories with topics. The goal >> is to leverage Google's API fully and transparently to the UPS user so that >> we make fewer calls and provide a better experience. You have some great >> use cases that haven't been brought up. Keep in mind that the PRs open >> right now are a "first draft" of the technology. Feel free to join in on >> the discussion about topics on aerogear-dev. It is really important we do >> this right and I think you can help with that. >> >> >> >> Summers >> >> >> >> >> - Kelvin >> >> >> ------------------------------------------------------------ >> --------------------------- >> From: aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman >> Sent: Monday, August 10, 2015 6:12 PM >> To: aerogear-users at lists.jboss.org >> Subject: Re: [Aerogear-users] categories have been hijacked >> >> >> >> > >> >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford >> wrote: >> >Setting "categories" in the push payload was working for android and ios >> in cordova push plugin 1.1.1. >> > >> >For version 2.0.2 "categories" only works for ios. >> > >> >It looks like "categories" is being hijacked in android for a GCM >> feature called "topics". >> > >> >I liked "categories". I was using it. Now it's gone. GCM topics is >> not a drop-in replacement. It's not the same thing. >> >> What do categories do that topics do not do? >> >> >New features should get new names and new commands. >> > >> >- Kelvin >> >> >> _______________________________________________ >> 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 >> >> >> >> _______________________________________________ >> 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/20160912/bbeb8141/attachment-0001.html From kelvin at qantel.com Mon Sep 12 15:13:59 2016 From: kelvin at qantel.com (Kelvin Lunsford) Date: Mon, 12 Sep 2016 19:13:59 +0000 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> Message-ID: This is not caused by the GSON bug. It is not a problem in Aerogear Android Store. Topics is more restrictive than JSON. When Topics was implemented this validation check was added to Aerogear Android Push: private static final String FCM_TOPIC_PATTERN = "[a-zA-Z0-9-_.~%]{1,900}"; private static void validateCategories(String... categories) { for (String category : categories) { if (!category.matches(FCM_TOPIC_PATTERN)) { throw new IllegalArgumentException(String.format("%s does not match %s", category, FCM_TOPIC_PATTERN)); } } } This validation check should not be required. Topics was supposed to be implemented into categories transparently. Instead of a validation check the Topic names should have been encoded (i.e. percent encoding) before being given to the Topics interface to avoid this Topics restriction. Category names should not be stored as Topic encoded because they might be used for non-Topic notifications (e.g. a push with a category and an alias). - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Daniel Passos Sent: Monday, September 12, 2016 9:10 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Hey Kelvin, It's a knowledge[1] bug fixed[2] in AeroGear Android Store cause by a GSON bug[3]. I'm going to create a new version of AeroGear Android Push library using the new Store version to fix this bug. [1] https://issues.jboss.org/browse/AGDROID-564 [2] https://github.com/aerogear/aerogear-android-store/pull/41 [3] https://github.com/google/gson/issues/210 On Mon, Sep 12, 2016 at 4:33 AM, Matthias Wessendorf > wrote: Hello, sorry for the problems you are encountering with our UPS and its client side libraries. I've created a JIRA ticket to capture the problem: https://issues.jboss.org/browse/AGDROID-565 greetings, Matthias On Fri, Sep 9, 2016 at 10:40 PM, Kelvin Lunsford > wrote: My categories no longer work on android because I use ":" characters in my category names. Last May aerogear-android-push:3.0.0 was released with Topics and now the android plugin refuses to accept my category names with non-Topic compatible characters. IOS still works with non-Topic compatible characters, but there is a regression in android. I warned you. Category names should have been percent encoded before applying them to the Topic interfaces in the plugin and UPS. It would have prevented the regression, but nobody did it. Now notifications are broken on the android version of my app. If I want to make it work with the current plugin I will have to change my category names to avoid using non-topic compatible characters. If I make the change it will affect my android and IOS mobile apps, and I will have to change the system that posts the notification requests to UPS so it also changes the names. If no one responds with a "No, wait, we'll fix it!" that is what I will do. - Kelvin From: Kelvin Lunsford Sent: Tuesday, August 18, 2015 3:25 PM To: 'aerogear-users at lists.jboss.org' Subject: RE: [Aerogear-users] categories have been hijacked You need topic compliant percent encoding/decoding functions to use on category names when setting them to/from topic names. You can encode by using the android.net.Uri.encode() function and replacing the characters missed by the encode() function. Uri.decode() will work as is. Equivalent encoding would have to be done in java for UPS when it accesses a topic. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 18, 2015 6:26 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: Summers, What happens if a category name is not GCM topic compatible? That is a good question. Currently you will get a error because it fails validation. We've created a JIRA to track this issue here : https://issues.jboss.org/browse/AGPUSH-1501 Keep the hits coming. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 11, 2015 10:03 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Kelvin, For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: Hi Summers, GCM topic messages go to all devices registered for the topic. Topic notifications cannot be restricted to an alias or list of aliases. The way it worked before, and still works on ios, you can send a command to UPS with an "alias" name AND a "categories" name and it will only go to devices that have registered using that "alias" name AND that "categories" name. UPS finds which devices meet the selection criteria and push notification requests are sent for those devices. Requests with aliases and categories can target specific users in a group. With real "categories" you can segment users into groups, so every device can be assigned a category, and sub-groups can be defined by using more than one category per device. This is useful for geographic or organizational targeting. I have no problem with GCM topics. Just make it a new feature. Give me back my categories. So the goal isn't to replace or hijack categories with topics. The goal is to leverage Google's API fully and transparently to the UPS user so that we make fewer calls and provide a better experience. You have some great use cases that haven't been brought up. Keep in mind that the PRs open right now are a "first draft" of the technology. Feel free to join in on the discussion about topics on aerogear-dev. It is really important we do this right and I think you can help with that. Summers - Kelvin --------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Monday, August 10, 2015 6:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: >Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. > >For version 2.0.2 "categories" only works for ios. > >It looks like "categories" is being hijacked in android for a GCM feature called "topics". > >I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing. What do categories do that topics do not do? >New features should get new names and new commands. > >- Kelvin _______________________________________________ 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 _______________________________________________ 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/20160912/8157749f/attachment-0001.html From matzew at apache.org Mon Sep 12 16:11:53 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 12 Sep 2016 22:11:53 +0200 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> Message-ID: On Mon, Sep 12, 2016 at 9:13 PM, Kelvin Lunsford wrote: > This is not caused by the GSON bug. It is not a problem in Aerogear > Android Store. > > > > Topics is more restrictive than JSON. > > > > When Topics was implemented this validation check was added to Aerogear > Android Push: > > > > private static final String FCM_TOPIC_PATTERN = > "[a-zA-Z0-9-_.~%]{1,900}"; > > > > private static void validateCategories(String... categories) { > > for (String category : categories) { > > if (!category.matches(FCM_TOPIC_PATTERN)) { > > throw new IllegalArgumentException(String.format("%s does > not match %s", category, FCM_TOPIC_PATTERN)); > > } > > } > > } > > > > This validation check should not be required. Topics was supposed to be > implemented into categories transparently. Instead of a validation check > the Topic names should have been encoded (i.e. percent encoding) before > being given to the Topics interface to avoid this Topics restriction. > feel free to send a pull request w/ the suggested behavior > Category names should not be stored as Topic encoded because they might > be used for non-Topic notifications (e.g. a push with a category and an > alias). > > > > - Kelvin > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Daniel Passos > *Sent:* Monday, September 12, 2016 9:10 AM > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > Hey Kelvin, > > It's a knowledge[1] bug fixed[2] in AeroGear Android Store cause by a GSON > bug[3]. I'm going to create a new version of AeroGear Android Push library > using the new Store version to fix this bug. > > [1] https://issues.jboss.org/browse/AGDROID-564 > [2] https://github.com/aerogear/aerogear-android-store/pull/41 > [3] https://github.com/google/gson/issues/210 > > > > On Mon, Sep 12, 2016 at 4:33 AM, Matthias Wessendorf > wrote: > > Hello, > > > > sorry for the problems you are encountering with our UPS and its client > side libraries. I've created a JIRA ticket to capture the problem: > > https://issues.jboss.org/browse/AGDROID-565 > > > > greetings, > > Matthias > > > > On Fri, Sep 9, 2016 at 10:40 PM, Kelvin Lunsford > wrote: > > My categories no longer work on android because I use ":" characters in my > category names. > > > > Last May aerogear-android-push:3.0.0 was released with Topics and now the > android plugin refuses to accept my category names with non-Topic > compatible characters. > > > > IOS still works with non-Topic compatible characters, but there is a > regression in android. > > > > I warned you. Category names should have been percent encoded before > applying them to the Topic interfaces in the plugin and UPS. It would have > prevented the regression, but nobody did it. > > > > Now notifications are broken on the android version of my app. > > > > If I want to make it work with the current plugin I will have to change my > category names to avoid using non-topic compatible characters. If I make > the change it will affect my android and IOS mobile apps, and I will have > to change the system that posts the notification requests to UPS so it also > changes the names. > > > > If no one responds with a "No, wait, we'll fix it!" that is what I will do. > > > > - Kelvin > > > > > > *From:* Kelvin Lunsford > *Sent:* Tuesday, August 18, 2015 3:25 PM > *To:* 'aerogear-users at lists.jboss.org' > *Subject:* RE: [Aerogear-users] categories have been hijacked > > > > You need topic compliant percent encoding/decoding functions to use on > category names when setting them to/from topic names. > > > > You can encode by using the android.net.Uri.encode() function and > replacing the characters missed by the encode() function. Uri.decode() > will work as is. > > > > Equivalent encoding would have to be done in java for UPS when it accesses > a topic. > > > > - Kelvin > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org ] *On > Behalf Of *Summers Pittman > *Sent:* Tuesday, August 18, 2015 6:26 AM > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > > > > > On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: > > Summers, > > > > What happens if a category name is not GCM topic compatible? > > That is a good question. Currently you will get a error because it fails > validation. We've created a JIRA to track this issue here : > https://issues.jboss.org/browse/AGPUSH-1501 > > > > Keep the hits coming. > > > > - Kelvin > > > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Summers Pittman > *Sent:* Tuesday, August 11, 2015 10:03 AM > > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > Kelvin, > > > > For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 > > > > On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: > > > > > > On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: > > Hi Summers, > > GCM topic messages go to all devices registered for the topic. Topic > notifications cannot be restricted to an alias or list of aliases. > > The way it worked before, and still works on ios, you can send a command > to UPS with an "alias" name AND a "categories" name and it will only go to > devices that have registered using that "alias" name AND that "categories" > name. UPS finds which devices meet the selection criteria and push > notification requests are sent for those devices. > > Requests with aliases and categories can target specific users in a group. > > With real "categories" you can segment users into groups, so every device > can be assigned a category, and sub-groups can be defined by using more > than one category per device. This is useful for geographic or > organizational targeting. > > I have no problem with GCM topics. Just make it a new feature. Give me > back my categories. > > > > So the goal isn't to replace or hijack categories with topics. The goal is > to leverage Google's API fully and transparently to the UPS user so that we > make fewer calls and provide a better experience. You have some great use > cases that haven't been brought up. Keep in mind that the PRs open right > now are a "first draft" of the technology. Feel free to join in on the > discussion about topics on aerogear-dev. It is really important we do this > right and I think you can help with that. > > > > Summers > > > > > - Kelvin > > > ------------------------------------------------------------ > --------------------------- > From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] On Behalf Of Summers Pittman > Sent: Monday, August 10, 2015 6:12 PM > To: aerogear-users at lists.jboss.org > Subject: Re: [Aerogear-users] categories have been hijacked > > > > > > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: > >Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > > >For version 2.0.2 "categories" only works for ios. > > > >It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > > >I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > > What do categories do that topics do not do? > > >New features should get new names and new commands. > > > >- Kelvin > > > _______________________________________________ > 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 > > > > > _______________________________________________ > 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 > > _______________________________________________ > 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/20160912/19fb28e4/attachment-0001.html From kelvin at qantel.com Mon Sep 12 17:39:32 2016 From: kelvin at qantel.com (Kelvin Lunsford) Date: Mon, 12 Sep 2016 21:39:32 +0000 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> Message-ID: <413279addc074cf4971d843f88258291@gozer.qantel.com> Matthias, Sounds like you're saying "if you don't like it fix it yourself". How rude. I'm a user. This is the user mailing list. For me I can make it work as it is. I'm just pointing out a regression. You can leave it as it is, but you should let your users know that category names will now be restricted to the characters that are accepted by Google Topics for topic names. You should also add the validation check to all the other devices to prevent invalid category names from being used by them. UPS is a multi-device platform and category names are used by all devices, not just Android. A restriction in one affects them all. Or you could ask the programmer who added Topics to categories to submit a pull request. Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf Sent: Monday, September 12, 2016 1:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked On Mon, Sep 12, 2016 at 9:13 PM, Kelvin Lunsford > wrote: This is not caused by the GSON bug. It is not a problem in Aerogear Android Store. Topics is more restrictive than JSON. When Topics was implemented this validation check was added to Aerogear Android Push: private static final String FCM_TOPIC_PATTERN = "[a-zA-Z0-9-_.~%]{1,900}"; private static void validateCategories(String... categories) { for (String category : categories) { if (!category.matches(FCM_TOPIC_PATTERN)) { throw new IllegalArgumentException(String.format("%s does not match %s", category, FCM_TOPIC_PATTERN)); } } } This validation check should not be required. Topics was supposed to be implemented into categories transparently. Instead of a validation check the Topic names should have been encoded (i.e. percent encoding) before being given to the Topics interface to avoid this Topics restriction. feel free to send a pull request w/ the suggested behavior Category names should not be stored as Topic encoded because they might be used for non-Topic notifications (e.g. a push with a category and an alias). - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Daniel Passos Sent: Monday, September 12, 2016 9:10 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Hey Kelvin, It's a knowledge[1] bug fixed[2] in AeroGear Android Store cause by a GSON bug[3]. I'm going to create a new version of AeroGear Android Push library using the new Store version to fix this bug. [1] https://issues.jboss.org/browse/AGDROID-564 [2] https://github.com/aerogear/aerogear-android-store/pull/41 [3] https://github.com/google/gson/issues/210 On Mon, Sep 12, 2016 at 4:33 AM, Matthias Wessendorf > wrote: Hello, sorry for the problems you are encountering with our UPS and its client side libraries. I've created a JIRA ticket to capture the problem: https://issues.jboss.org/browse/AGDROID-565 greetings, Matthias On Fri, Sep 9, 2016 at 10:40 PM, Kelvin Lunsford > wrote: My categories no longer work on android because I use ":" characters in my category names. Last May aerogear-android-push:3.0.0 was released with Topics and now the android plugin refuses to accept my category names with non-Topic compatible characters. IOS still works with non-Topic compatible characters, but there is a regression in android. I warned you. Category names should have been percent encoded before applying them to the Topic interfaces in the plugin and UPS. It would have prevented the regression, but nobody did it. Now notifications are broken on the android version of my app. If I want to make it work with the current plugin I will have to change my category names to avoid using non-topic compatible characters. If I make the change it will affect my android and IOS mobile apps, and I will have to change the system that posts the notification requests to UPS so it also changes the names. If no one responds with a "No, wait, we'll fix it!" that is what I will do. - Kelvin From: Kelvin Lunsford Sent: Tuesday, August 18, 2015 3:25 PM To: 'aerogear-users at lists.jboss.org' Subject: RE: [Aerogear-users] categories have been hijacked You need topic compliant percent encoding/decoding functions to use on category names when setting them to/from topic names. You can encode by using the android.net.Uri.encode() function and replacing the characters missed by the encode() function. Uri.decode() will work as is. Equivalent encoding would have to be done in java for UPS when it accesses a topic. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 18, 2015 6:26 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: Summers, What happens if a category name is not GCM topic compatible? That is a good question. Currently you will get a error because it fails validation. We've created a JIRA to track this issue here : https://issues.jboss.org/browse/AGPUSH-1501 Keep the hits coming. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 11, 2015 10:03 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Kelvin, For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: Hi Summers, GCM topic messages go to all devices registered for the topic. Topic notifications cannot be restricted to an alias or list of aliases. The way it worked before, and still works on ios, you can send a command to UPS with an "alias" name AND a "categories" name and it will only go to devices that have registered using that "alias" name AND that "categories" name. UPS finds which devices meet the selection criteria and push notification requests are sent for those devices. Requests with aliases and categories can target specific users in a group. With real "categories" you can segment users into groups, so every device can be assigned a category, and sub-groups can be defined by using more than one category per device. This is useful for geographic or organizational targeting. I have no problem with GCM topics. Just make it a new feature. Give me back my categories. So the goal isn't to replace or hijack categories with topics. The goal is to leverage Google's API fully and transparently to the UPS user so that we make fewer calls and provide a better experience. You have some great use cases that haven't been brought up. Keep in mind that the PRs open right now are a "first draft" of the technology. Feel free to join in on the discussion about topics on aerogear-dev. It is really important we do this right and I think you can help with that. Summers - Kelvin --------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Monday, August 10, 2015 6:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: >Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. > >For version 2.0.2 "categories" only works for ios. > >It looks like "categories" is being hijacked in android for a GCM feature called "topics". > >I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing. What do categories do that topics do not do? >New features should get new names and new commands. > >- Kelvin _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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/20160912/57e77e69/attachment-0001.html From matzew at apache.org Mon Sep 12 17:53:05 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 12 Sep 2016 23:53:05 +0200 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: <413279addc074cf4971d843f88258291@gozer.qantel.com> References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> <297f6301e6774d85a85f5576c94e117b@gozer.qantel.com> <413279addc074cf4971d843f88258291@gozer.qantel.com> Message-ID: On Mon, Sep 12, 2016 at 11:39 PM, Kelvin Lunsford wrote: > Matthias, > > > > Sounds like you're saying "if you don't like it fix it yourself". How > rude. > nope, not at all. but perhaps we as a larger group can turn your PR into a proper fix. >From the critics earlier I think you have an idea how the fix should look like, so why not sending a PR? -Matthias > > > I'm a user. This is the user mailing list. For me I can make it work as > it is. I'm just pointing out a regression. > > > > You can leave it as it is, but you should let your users know that > category names will now be restricted to the characters that are accepted > by Google Topics for topic names. You should also add the validation check > to all the other devices to prevent invalid category names from being used > by them. UPS is a multi-device platform and category names are used by all > devices, not just Android. A restriction in one affects them all. > > > > Or you could ask the programmer who added Topics to categories to submit a > pull request. > > > > Kelvin > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Matthias Wessendorf > *Sent:* Monday, September 12, 2016 1:12 PM > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > > > > > On Mon, Sep 12, 2016 at 9:13 PM, Kelvin Lunsford > wrote: > > This is not caused by the GSON bug. It is not a problem in Aerogear > Android Store. > > > > Topics is more restrictive than JSON. > > > > When Topics was implemented this validation check was added to Aerogear > Android Push: > > > > private static final String FCM_TOPIC_PATTERN = > "[a-zA-Z0-9-_.~%]{1,900}"; > > > > private static void validateCategories(String... categories) { > > for (String category : categories) { > > if (!category.matches(FCM_TOPIC_PATTERN)) { > > throw new IllegalArgumentException(String.format("%s does > not match %s", category, FCM_TOPIC_PATTERN)); > > } > > } > > } > > > > This validation check should not be required. Topics was supposed to be > implemented into categories transparently. Instead of a validation check > the Topic names should have been encoded (i.e. percent encoding) before > being given to the Topics interface to avoid this Topics restriction. > > > > feel free to send a pull request w/ the suggested behavior > > > > Category names should not be stored as Topic encoded because they might > be used for non-Topic notifications (e.g. a push with a category and an > alias). > > > > - Kelvin > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Daniel Passos > *Sent:* Monday, September 12, 2016 9:10 AM > > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > Hey Kelvin, > > It's a knowledge[1] bug fixed[2] in AeroGear Android Store cause by a GSON > bug[3]. I'm going to create a new version of AeroGear Android Push library > using the new Store version to fix this bug. > > [1] https://issues.jboss.org/browse/AGDROID-564 > [2] https://github.com/aerogear/aerogear-android-store/pull/41 > [3] https://github.com/google/gson/issues/210 > > > > On Mon, Sep 12, 2016 at 4:33 AM, Matthias Wessendorf > wrote: > > Hello, > > > > sorry for the problems you are encountering with our UPS and its client > side libraries. I've created a JIRA ticket to capture the problem: > > https://issues.jboss.org/browse/AGDROID-565 > > > > greetings, > > Matthias > > > > On Fri, Sep 9, 2016 at 10:40 PM, Kelvin Lunsford > wrote: > > My categories no longer work on android because I use ":" characters in my > category names. > > > > Last May aerogear-android-push:3.0.0 was released with Topics and now the > android plugin refuses to accept my category names with non-Topic > compatible characters. > > > > IOS still works with non-Topic compatible characters, but there is a > regression in android. > > > > I warned you. Category names should have been percent encoded before > applying them to the Topic interfaces in the plugin and UPS. It would have > prevented the regression, but nobody did it. > > > > Now notifications are broken on the android version of my app. > > > > If I want to make it work with the current plugin I will have to change my > category names to avoid using non-topic compatible characters. If I make > the change it will affect my android and IOS mobile apps, and I will have > to change the system that posts the notification requests to UPS so it also > changes the names. > > > > If no one responds with a "No, wait, we'll fix it!" that is what I will do. > > > > - Kelvin > > > > > > *From:* Kelvin Lunsford > *Sent:* Tuesday, August 18, 2015 3:25 PM > *To:* 'aerogear-users at lists.jboss.org' > *Subject:* RE: [Aerogear-users] categories have been hijacked > > > > You need topic compliant percent encoding/decoding functions to use on > category names when setting them to/from topic names. > > > > You can encode by using the android.net.Uri.encode() function and > replacing the characters missed by the encode() function. Uri.decode() > will work as is. > > > > Equivalent encoding would have to be done in java for UPS when it accesses > a topic. > > > > - Kelvin > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org ] *On > Behalf Of *Summers Pittman > *Sent:* Tuesday, August 18, 2015 6:26 AM > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > > > > > On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: > > Summers, > > > > What happens if a category name is not GCM topic compatible? > > That is a good question. Currently you will get a error because it fails > validation. We've created a JIRA to track this issue here : > https://issues.jboss.org/browse/AGPUSH-1501 > > > > Keep the hits coming. > > > > - Kelvin > > > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] *On Behalf Of *Summers Pittman > *Sent:* Tuesday, August 11, 2015 10:03 AM > > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > Kelvin, > > > > For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 > > > > On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: > > > > > > On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: > > Hi Summers, > > GCM topic messages go to all devices registered for the topic. Topic > notifications cannot be restricted to an alias or list of aliases. > > The way it worked before, and still works on ios, you can send a command > to UPS with an "alias" name AND a "categories" name and it will only go to > devices that have registered using that "alias" name AND that "categories" > name. UPS finds which devices meet the selection criteria and push > notification requests are sent for those devices. > > Requests with aliases and categories can target specific users in a group. > > With real "categories" you can segment users into groups, so every device > can be assigned a category, and sub-groups can be defined by using more > than one category per device. This is useful for geographic or > organizational targeting. > > I have no problem with GCM topics. Just make it a new feature. Give me > back my categories. > > > > So the goal isn't to replace or hijack categories with topics. The goal is > to leverage Google's API fully and transparently to the UPS user so that we > make fewer calls and provide a better experience. You have some great use > cases that haven't been brought up. Keep in mind that the PRs open right > now are a "first draft" of the technology. Feel free to join in on the > discussion about topics on aerogear-dev. It is really important we do this > right and I think you can help with that. > > > > Summers > > > > > - Kelvin > > > ------------------------------------------------------------ > --------------------------- > From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users- > bounces at lists.jboss.org] On Behalf Of Summers Pittman > Sent: Monday, August 10, 2015 6:12 PM > To: aerogear-users at lists.jboss.org > Subject: Re: [Aerogear-users] categories have been hijacked > > > > > > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: > >Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > > >For version 2.0.2 "categories" only works for ios. > > > >It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > > >I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > > What do categories do that topics do not do? > > >New features should get new names and new commands. > > > >- Kelvin > > > _______________________________________________ > 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 > > > > > _______________________________________________ > 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 > > > _______________________________________________ > 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 > > -- 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/20160912/3f32901f/attachment-0001.html From matzew at apache.org Tue Sep 13 04:18:04 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 13 Sep 2016 10:18:04 +0200 Subject: [Aerogear-users] [aerogear-dev] aerogear-cordova-push 3.0.1 In-Reply-To: References: Message-ID: Let's ship it! On Fri, Sep 9, 2016 at 1:43 PM, Erik Jan de Wit wrote: > Hi, > > We fixed a couple of bug on aerogear-cordova-push and would like to > release it. The 3.0.x branch is ready for testing > > -- > Cheers, > Erik Jan > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- 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/20160913/d1874bc6/attachment.html From matzew at apache.org Tue Sep 13 04:20:27 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 13 Sep 2016 10:20:27 +0200 Subject: [Aerogear-users] [aerogear-dev] [RELEASE] Unifiedpush 1.2.0-alpha.2 In-Reply-To: References: Message-ID: I've clicked the button, and will upload the missing bits to GH -Matthias On Mon, Sep 12, 2016 at 9:56 AM, Matthias Wessendorf wrote: > Besides that, I've tested the release (via docker), and it works fine > > +1 on releasing this > > On Mon, Sep 12, 2016 at 9:46 AM, Matthias Wessendorf > wrote: > >> On this tag, we need the signed artifacts: >> https://github.com/aerogear/aerogear-unifiedpush-server/rele >> ases/tag/1.2.0-alpha.2 >> >> >> >> On Fri, Sep 9, 2016 at 1:05 PM, Sebastien Blanc >> wrote: >> >>> Hi Folks, >>> >>> I'm happy to announce that the UPS 1.2.0-alpha.2 release has been >>> staged. >>> >>> It's available here : >>> >>> https://repository.jboss.org/nexus/content/repositories/jbos >>> s_releases_staging_profile-8977 >>> >>> Test and have fun ... >>> >>> I should be pushed next mid-week (along with docker image updates) >>> >>> Sebi >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> >> -- >> 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/20160913/1b20449f/attachment.html From edewit at redhat.com Tue Sep 13 12:01:21 2016 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 13 Sep 2016 18:01:21 +0200 Subject: [Aerogear-users] [aerogear-dev] aerogear-cordova-push 3.0.1 In-Reply-To: References: Message-ID: I've hit the magic buttons On Tue, Sep 13, 2016 at 10:18 AM, Matthias Wessendorf wrote: > Let's ship it! > > On Fri, Sep 9, 2016 at 1:43 PM, Erik Jan de Wit wrote: > >> Hi, >> >> We fixed a couple of bug on aerogear-cordova-push and would like to >> release it. The 3.0.x branch is ready for testing >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > 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 > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160913/9d21354c/attachment.html From sachidananda.patra at hp.com Thu Sep 22 04:51:44 2016 From: sachidananda.patra at hp.com (Sachidananda Patra) Date: Thu, 22 Sep 2016 01:51:44 -0700 (MST) Subject: [Aerogear-users] =?utf-8?q?Failed_to_process_phase_PARSE_of_deplo?= =?utf-8?q?yment_=E2=80=9Cunifiedpush-server-wildfly=2Ewar=E2=80=9D?= Message-ID: <1474534304792-902.post@n5.nabble.com> *I found the below error while unifiedpush-auth-server.war and unifiedpush-server-wildfly.war deployed to jboss-wildfly-10.1.0\standalone\deployments. >> Prerequisite jboss-wildfly-10.1.0 server is running in below mode* $ ./standalone.sh --server-config=standalone-full.xml15:54:10,589 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "unifiedpush-server-wildfly.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) ... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[20,1] Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment' at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89) ... 6 more----------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- ----------------------------------------------------------- --------------Details Console Logs : USER ~$ cd D:/jboss-wildfly-10.1.0/bin USER /cygdrive/d/jboss-wildfly-10.1.0/bin$ ./standalone.sh --server-config=standalone-full.xml========================================================================= JBoss Bootstrap Environment JBOSS_HOME: D:\jboss-wildfly-10.1.0 JAVA: /cygdrive/c/Program Files (x86)/Java/jdk1.8.0_31/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 15:52:59,638 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final15:52:59,857 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final15:52:59,920 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting15:53:02,124 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)15:53:02,172 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.4.0.Final15:53:02,180 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.4.0.Final15:53:02,232 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)15:53:02,263 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors15:53:02,372 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.15:53:02,441 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem15:53:02,446 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]15:53:02,480 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.15:53:02,501 INFO [org.jboss.as.security] (MSC service thread 1-6) WFLYSEC0001: Current PicketBox version=4.9.6.Final15:53:02,510 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem15:53:02,511 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem15:53:02,521 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)15:53:02,553 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.0.Final starting15:53:02,553 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h215:53:02,581 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension15:53:02,606 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service15:53:02,606 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]15:53:02,651 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.21.Final15:53:02,756 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.15:53:02,757 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.15:53:02,833 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path 'D:\jboss-wildfly-10.1.0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']15:53:02,870 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.15:53:02,871 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting15:53:03,041 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:808015:53:03,528 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore D:\jboss-wildfly-10.1.0\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost15:53:03,553 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory D:\jboss-wildfly-10.1.0\standalone\deployments15:53:03,658 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]15:53:03,680 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB Service started15:53:03,688 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.15:53:03,773 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final15:53:03,834 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 69) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.15:53:03,835 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 69) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.15:53:03,838 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 64) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.15:53:03,839 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 64) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.15:53:03,841 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.15:53:03,841 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 65) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.15:53:03,923 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:844315:53:04,108 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\journal,bindingsDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\bindings,largeMessagesDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\largemessages,pagingDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\paging)15:53:04,185 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal15:53:04,853 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE15:53:04,897 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP15:53:04,935 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)15:53:04,968 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ15:53:04,971 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP15:53:06,397 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor15:53:06,398 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor15:53:06,403 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor15:53:06,400 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor15:53:06,558 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live15:53:06,559 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [nodeID=cc5214e7-78d4-11e6-a2b4-79dfc4ded2f5]15:53:06,561 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 69) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue15:53:06,706 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ15:53:06,733 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 65) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory15:53:06,734 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory15:53:06,746 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA15:53:06,836 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) Resource adaptor started15:53:06,836 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra15:53:06,838 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]15:53:06,838 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory15:53:07,164 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management15:53:07,165 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:999015:53:07,166 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 7916ms - Started 370 of 615 services (408 services are lazy, passive or on-demand) 15:54:03,799 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location D:\jboss-wildfly-10.1.0\standalone\data\content\e8\0ec98a850ae6460df834d03dc1c594dfa5c3e2\content 15:53:06,838 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]15:53:06,838 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory15:53:07,164 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management15:53:07,165 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:999015:53:07,166 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 7916ms - Started 370 of 615 services (408 services are lazy, passive or on-demand) 15:54:03,799 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location D:\jboss-wildfly-10.1.0\standalone\data\content\e8\0ec98a850ae6460df834d03dc1c594dfa5c3e2\content15:54:03,949 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location D:\jboss-wildfly-10.1.0\standalone\data\content\03\3e00399f37e4aeec988109e2171565d5aedfb2\content15:54:03,967 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "unifiedpush-auth-server.war" (runtime-name: "unifiedpush-auth-server.war")15:54:03,967 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "unifiedpush-server-wildfly.war" (runtime-name: "unifiedpush-server-wildfly.war")15:54:07,536 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in /D:/jboss-wildfly-10.1.0/bin/content/unifiedpush-auth-server.war/WEB-INF/lib/liquibase-core-3.3.5.jar does not point to a valid jar for a Class-Path reference.15:54:07,669 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for keycloak-default15:54:08,413 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice.15:54:08,414 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice.15:54:08,415 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war" is using a private module ("org.infinispan:main") which may be changed or removed in future versions without notice.15:54:10,579 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Read persistence.xml for unifiedpush-default15:54:10,589 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit. "unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "unifiedpush-server-wildfly.war"at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xmlat org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)... 5 moreCaused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xmlat org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)... 6 moreCaused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[20,1]Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)at org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)... 6 more 15:54:11,627 INFO [org.keycloak.services.resources.KeycloakApplication] (ServerService Thread Pool -- 76) Load config from vfs:/D:/jboss-wildfly-10.1.0/bin/content/unifiedpush-auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json15:54:11,988 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 76) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./auth: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./auth: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:162) at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2246) at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:304) at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:245) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:113) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117) at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78) at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250) at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133) at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:546) at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:559) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) ... 6 moreCaused by: java.lang.RuntimeException: Failed to connect to database at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:184) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:35) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:25) at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99) at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:34) at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:16) at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99) at org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:70) at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:163) at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:40) at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:31) at org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:157) at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40) at org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:87) at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.(UpsKeycloakApplication.java:35) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:150) ... 29 moreCaused by: javax.naming.NameNotFoundException: datasources/KeycloakDS -- service jboss.naming.context.java.jboss.datasources.KeycloakDS at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) at javax.naming.InitialContext.lookup(InitialContext.java:417) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:177) ... 49 more 15:54:11,994 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "unifiedpush-auth-server.war")]) - failure description: { "WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./auth" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./auth: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) Caused by: java.lang.RuntimeException: Failed to connect to database Caused by: javax.naming.NameNotFoundException: datasources/KeycloakDS -- service jboss.naming.context.java.jboss.datasources.KeycloakDS"}, "WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.deployment.default-server.default-host./auth"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}15:54:11,994 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "unifiedpush-server-wildfly.war")]) - failure description: { "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"unifiedpush-server-wildfly.war\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file D:\\jboss-wildfly-10.1.0\\standalone\\tmp\\vfs\\temp\\temp46e687319f527ed3\\content-a52cb55da5bbb09d\\WEB-INF\\hornetq-jms.xml Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not parse file D:\\jboss-wildfly-10.1.0\\standalone\\tmp\\vfs\\temp\\temp46e687319f527ed3\\content-a52cb55da5bbb09d\\WEB-INF\\hornetq-jms.xml Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[20,1]Message: Unexpected element '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}, "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}15:54:12,053 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "unifiedpush-server-wildfly.war" (runtime-name : "unifiedpush-server-wildfly.war")15:54:12,053 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "unifiedpush-auth-server.war" (runtime-name : "unifiedpush-auth-server.war")15:54:12,053 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status reportWFLYCTL0186: Services which failed to start: service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "unifiedpush-server-wildfly.war"service jboss.undertow.deployment.default-server.default-host./auth: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./auth: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902.html Sent from the aerogear-users mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160922/447eeaf8/attachment-0001.html From matzew at apache.org Mon Sep 26 03:54:05 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 26 Sep 2016 09:54:05 +0200 Subject: [Aerogear-users] =?utf-8?q?Failed_to_process_phase_PARSE_of_deplo?= =?utf-8?q?yment_=E2=80=9Cunifiedpush-server-wildfly=2Ewar=E2=80=9D?= In-Reply-To: <1474534304792-902.post@n5.nabble.com> References: <1474534304792-902.post@n5.nabble.com> Message-ID: Hi, what version are you using? Version 1.1.x is not running on WF 10, but version 1.2.0-alpha is. For instance, take a look here: https://github.com/aerogear/dockerfiles/blob/master/wildfly/Dockerfile#L2 -Matthias On Thu, Sep 22, 2016 at 10:51 AM, Sachidananda Patra < sachidananda.patra at hp.com> wrote: > *I found the below error while unifiedpush-auth-server.war and > unifiedpush-server-wildfly.war deployed to > jboss-wildfly-10.1.0\standalone\deployments. >> Prerequisite > jboss-wildfly-10.1.0 server is running in below mode* $ ./standalone.sh > --server-config=standalone-full.xml 15:54:10,589 ERROR > [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to > start service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: > org.jboss.msc.service.StartException in service jboss.deployment.unit." > unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153: Failed to process > phase PARSE of deployment "unifiedpush-server-wildfly.war" at > org.jboss.as.server.deployment.DeploymentUnitPhaseService.start( > DeploymentUnitPhaseService.java:154) at org.jboss.msc.service. > ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run( > ServiceControllerImpl.java:1881) at java.util.concurrent. > ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.as.server. > deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not > parse file D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\ > temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml at > org.wildfly.extension.messaging.activemq.deployment. > MessagingXmlParsingDeploymentUnitProcessor.deploy( > MessagingXmlParsingDeploymentUnitProcessor.java:98) at > org.jboss.as.server.deployment.DeploymentUnitPhaseService.start( > DeploymentUnitPhaseService.java:147) ... 5 more Caused by: > org.jboss.as.server.deployment.DeploymentUnitProcessingException: > WFLYMSGAMQ0055: Could not parse file D:\jboss-wildfly-10.1.0\ > standalone\tmp\vfs\temp\temp46e687319f527ed3\content- > a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml at org.wildfly.extension. > messaging.activemq.deployment.MessagingXmlParsingDeploymentU > nitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at > [row,col]:[20,1] Message: Unexpected element '{urn:jboss:messaging- > deployment:1.0}messaging-deployment' at org.jboss.staxmapper. > XMLMapperImpl.processNested(XMLMapperImpl.java:108) at > org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.wildfly.extension.messaging.activemq.deployment. > MessagingXmlParsingDeploymentUnitProcessor.deploy( > MessagingXmlParsingDeploymentUnitProcessor.java:89) ... 6 more > ----------------------------------------------------------------------------------------- > ----------------------------------------------------------------------------------- > ----------------------------------------------------------- > -------------- Details Console Logs : USER ~ $ cd > D:/jboss-wildfly-10.1.0/bin USER /cygdrive/d/jboss-wildfly-10.1.0/bin $ > ./standalone.sh --server-config=standalone-full.xml > ========================================================================= > JBoss Bootstrap Environment JBOSS_HOME: D:\jboss-wildfly-10.1.0 JAVA: > /cygdrive/c/Program Files (x86)/Java/jdk1.8.0_31/bin/java JAVA_OPTS: > -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m > -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman > -Djava.awt.headless=true ============================== > =========================================== 15:52:59,638 INFO > [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final 15:52:59,857 > INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 15:52:59,920 INFO > [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full > 10.1.0.Final (WildFly Core 2.2.0.Final) starting 15:53:02,124 INFO > [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http > management service using socket-binding (management-http) 15:53:02,172 INFO > [org.xnio] (MSC service thread 1-5) XNIO version 3.4.0.Final 15:53:02,180 > INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation > Version 3.4.0.Final 15:53:02,232 INFO [org.jboss.as.connector.subsystems.datasources] > (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant > driver class org.h2.Driver (version 1.3) 15:53:02,263 INFO [ > org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: > Worker 'default' has auto-configured to 8 core threads with 64 task threads > based on your 4 available processors 15:53:02,372 INFO > [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) > WFLYCLINF0001: Activating Infinispan subsystem. 15:53:02,441 INFO > [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: > Activating Security Subsystem 15:53:02,446 INFO [org.jboss.as.jsf] > (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF > Implementations: [main] 15:53:02,480 WARN [org.jboss.as.txn] (ServerService > Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the > default value. Please make sure it is unique. 15:53:02,501 INFO > [org.jboss.as.security] (MSC service thread 1-6) WFLYSEC0001: Current > PicketBox version=4.9.6.Final 15:53:02,510 INFO [org.jboss.as.naming] > (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem > 15:53:02,511 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- > 42) WFLYIIOP0001: Activating IIOP Subsystem 15:53:02,521 INFO > [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA > Subsystem (WildFly/IronJacamar 1.3.4.Final) 15:53:02,553 INFO > [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: > Undertow 1.4.0.Final starting 15:53:02,553 INFO [org.jboss.as.connector.deployers.jdbc] > (MSC service thread 1-1) WFLYJCA0018: Started Driver service with > driver-name = h2 15:53:02,581 INFO [org.jboss.as.webservices] > (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices > Extension 15:53:02,606 INFO [org.jboss.as.naming] (MSC service thread 1-2) > WFLYNAM0003: Starting Naming Service 15:53:02,606 INFO > [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound > mail session [java:jboss/mail/Default] 15:53:02,651 INFO > [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version > 4.0.21.Final 15:53:02,756 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) > WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size > of 64 (per class), which is derived from thread worker pool sizing. > 15:53:02,757 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: > Strict pool mdb-strict-max-pool is using a max instance size of 16 (per > class), which is derived from the number of CPUs on this host. 15:53:02,833 > INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) > WFLYUT0014: Creating file handler for path 'D:\jboss-wildfly-10.1.0/welcome-content' > with options [directory-listing: 'false', follow-symlink: 'false', > case-sensitive: 'true', safe-symlink-paths: '[]'] 15:53:02,870 INFO > [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: > Started server default-server. 15:53:02,871 INFO [org.wildfly.extension.undertow] > (MSC service thread 1-4) WFLYUT0018: Host default-host starting > 15:53:03,041 INFO [org.wildfly.extension.undertow] (MSC service thread > 1-7) WFLYUT0006: Undertow HTTP listener default listening on > 127.0.0.1:8080 15:53:03,528 WARN [org.jboss.as.domain.management.security] > (MSC service thread 1-5) WFLYDM0111: Keystore D:\jboss-wildfly-10.1.0\ > standalone\configuration\application.keystore not found, it will be auto > generated on first use with a self signed certificate for host localhost > 15:53:03,553 INFO [org.jboss.as.server.deployment.scanner] (MSC service > thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory > D:\jboss-wildfly-10.1.0\standalone\deployments 15:53:03,658 INFO > [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) > WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 15:53:03,680 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-1) > WFLYIIOP0009: CORBA ORB Service started 15:53:03,688 INFO > [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) > WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to > using pure Java NIO. 15:53:03,773 INFO [org.infinispan.factories.GlobalComponentRegistry] > (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan > 'Chakra' 8.2.4.Final 15:53:03,834 INFO [org.infinispan.configuration. > cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 69) > ISPN000152: Passivation configured without an eviction policy being > selected. Only manually evicted entities will be passivated. 15:53:03,835 > INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] > (ServerService Thread Pool -- 69) ISPN000152: Passivation configured > without an eviction policy being selected. Only manually evicted entities > will be passivated. 15:53:03,838 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] > (ServerService Thread Pool -- 64) ISPN000152: Passivation configured > without an eviction policy being selected. Only manually evicted entities > will be passivated. 15:53:03,839 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] > (ServerService Thread Pool -- 64) ISPN000152: Passivation configured > without an eviction policy being selected. Only manually evicted entities > will be passivated. 15:53:03,841 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] > (ServerService Thread Pool -- 65) ISPN000152: Passivation configured > without an eviction policy being selected. Only manually evicted entities > will be passivated. 15:53:03,841 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] > (ServerService Thread Pool -- 65) ISPN000152: Passivation configured > without an eviction policy being selected. Only manually evicted entities > will be passivated. 15:53:03,923 INFO [org.wildfly.extension.undertow] > (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https > listening on 127.0.0.1:8443 15:53:04,108 INFO > [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- > 64) AMQ221000: live Message Broker is starting with configuration Broker > Configuration (clustered=false,journalDirectory=D:\jboss- > wildfly-10.1.0\standalone\data\activemq\journal, > bindingsDirectory=D:\jboss-wildfly-10.1.0\standalone\ > data\activemq\bindings,largeMessagesDirectory=D:\jboss-wildfly-10.1.0\ > standalone\data\activemq\largemessages,pagingDirectory= > D:\jboss-wildfly-10.1.0\standalone\data\activemq\paging) 15:53:04,185 > INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool > -- 64) AMQ221013: Using NIO Journal 15:53:04,853 INFO > [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- > 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol > support for: CORE 15:53:04,897 INFO [org.apache.activemq.artemis.core.server] > (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: > [artemis-amqp-protocol]. Adding protocol support for: AMQP 15:53:04,935 > INFO [org.jboss.ws.common.management] (MSC service thread 1-4) > JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6) 15:53:04,968 > INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool > -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding > protocol support for: HORNETQ 15:53:04,971 INFO > [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- > 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding > protocol support for: STOMP 15:53:06,397 INFO [org.wildfly.extension.messaging-activemq] > (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for > activemq-remoting protocol handled by http-acceptor acceptor 15:53:06,398 > INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) > WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol > handled by http-acceptor acceptor 15:53:06,403 INFO [org.wildfly.extension.messaging-activemq] > (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for > activemq-remoting protocol handled by http-acceptor-throughput acceptor > 15:53:06,400 INFO [org.wildfly.extension.messaging-activemq] (MSC service > thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting > protocol handled by http-acceptor-throughput acceptor 15:53:06,558 INFO > [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- > 64) AMQ221007: Server is now live 15:53:06,559 INFO > [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- > 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version > 1.1.0.wildfly-017 [nodeID=cc5214e7-78d4-11e6-a2b4-79dfc4ded2f5] > 15:53:06,561 INFO [org.apache.activemq.artemis.core.server] > (ServerService Thread Pool -- 69) AMQ221003: trying to deploy queue > jms.queue.ExpiryQueue 15:53:06,706 INFO [org.apache.activemq.artemis.core.server] > (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue > jms.queue.DLQ 15:53:06,733 INFO [org.wildfly.extension.messaging-activemq] > (ServerService Thread Pool -- 65) WFLYMSGAMQ0002: Bound messaging object to > jndi name java:/ConnectionFactory 15:53:06,734 INFO [org.wildfly.extension.messaging-activemq] > (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to > jndi name java:jboss/exported/jms/RemoteConnectionFactory 15:53:06,746 > INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) > WFLYJCA0007: Registered connection factory java:/JmsXA 15:53:06,836 INFO > [org.apache.activemq.artemis.ra] (MSC service thread 1-3) Resource > adaptor started 15:53:06,836 INFO [org.jboss.as.connector. > services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] > (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra > 15:53:06,838 INFO [org.jboss.as.connector.deployment] (MSC service thread > 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 15:53:06,838 > INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) > WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 15:53:07,164 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: > Http management interface listening on http://127.0.0.1:9990/management > 15:53:07,165 INFO [ > org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console > listening on http://127.0.0.1:9990 15:53:07,166 INFO [org.jboss.as] > (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly > Core 2.2.0.Final) started in 7916ms - Started 370 of 615 services (408 > services are lazy, passive or on-demand) 15:54:03,799 INFO > [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: > Content added at location D:\jboss-wildfly-10.1.0\ > standalone\data\content\e8\0ec98a850ae6460df834d03dc1c594dfa5c3e2\content > 15:53:06,838 INFO [org.jboss.as.connector.deployment] (MSC service thread > 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 15:53:06,838 > INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) > WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory > 15:53:07,164 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: > Http management interface listening on http://127.0.0.1:9990/management > 15:53:07,165 INFO [ > org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console > listening on http://127.0.0.1:9990 15:53:07,166 INFO [org.jboss.as] > (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly > Core 2.2.0.Final) started in 7916ms - Started 370 of 615 services (408 > services are lazy, passive or on-demand) 15:54:03,799 INFO > [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: > Content added at location D:\jboss-wildfly-10.1.0\ > standalone\data\content\e8\0ec98a850ae6460df834d03dc1c594dfa5c3e2\content > 15:54:03,949 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) > WFLYDR0001: Content added at location D:\jboss-wildfly-10.1.0\ > standalone\data\content\03\3e00399f37e4aeec988109e2171565d5aedfb2\content > 15:54:03,967 INFO [org.jboss.as.server.deployment] (MSC service thread > 1-6) WFLYSRV0027: Starting deployment of "unifiedpush-auth-server.war" > (runtime-name: "unifiedpush-auth-server.war") 15:54:03,967 INFO > [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: > Starting deployment of "unifiedpush-server-wildfly.war" (runtime-name: > "unifiedpush-server-wildfly.war") 15:54:07,536 WARN [org.jboss.as.server.deployment] > (MSC service thread 1-6) WFLYSRV0059: Class Path entry > lib/snakeyaml-1.13.jar in /D:/jboss-wildfly-10.1.0/bin/ > content/unifiedpush-auth-server.war/WEB-INF/lib/liquibase-core-3.3.5.jar > does not point to a valid jar for a Class-Path reference. 15:54:07,669 INFO > [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read > persistence.xml for keycloak-default 15:54:08,413 WARN > [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: > Deployment "deployment.unifiedpush-auth-server.war" is using a private > module ("org.codehaus.jackson.jackson-core-asl:main") which may be > changed or removed in future versions without notice. 15:54:08,414 WARN > [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: > Deployment "deployment.unifiedpush-auth-server.war" is using a private > module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be > changed or removed in future versions without notice. 15:54:08,415 WARN > [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: > Deployment "deployment.unifiedpush-auth-server.war" is using a private > module ("org.infinispan:main") which may be changed or removed in future > versions without notice. 15:54:10,579 INFO [org.jboss.as.jpa] (MSC service > thread 1-7) WFLYJPA0002: Read persistence.xml for unifiedpush-default > 15:54:10,589 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) > MSC000001: Failed to start service jboss.deployment.unit." > unifiedpush-server-wildfly.war".PARSE: org.jboss.msc.service.StartException > in service jboss.deployment.unit. "unifiedpush-server-wildfly.war".PARSE: > WFLYSRV0153: Failed to process phase PARSE of deployment > "unifiedpush-server-wildfly.war" at org.jboss.as.server.deployment. > DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at > org.jboss.msc.service.ServiceControllerImpl$StartTask.startService( > ServiceControllerImpl.java:1948) at org.jboss.msc.service. > ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) Caused by: org.jboss.as.server. > deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not > parse file D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\ > temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml at > org.wildfly.extension.messaging.activemq.deployment. > MessagingXmlParsingDeploymentUnitProcessor.deploy( > MessagingXmlParsingDeploymentUnitProcessor.java:98) at > org.jboss.as.server.deployment.DeploymentUnitPhaseService.start( > DeploymentUnitPhaseService.java:147) ... 5 more Caused by: > org.jboss.as.server.deployment.DeploymentUnitProcessingException: > WFLYMSGAMQ0055: Could not parse file D:\jboss-wildfly-10.1.0\ > standalone\tmp\vfs\temp\temp46e687319f527ed3\content- > a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml at org.wildfly.extension. > messaging.activemq.deployment.MessagingXmlParsingDeploymentU > nitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95) > ... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at > [row,col]:[20,1] Message: Unexpected element '{urn:jboss:messaging- > deployment:1.0}messaging-deployment' at org.jboss.staxmapper. > XMLMapperImpl.processNested(XMLMapperImpl.java:108) at > org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.wildfly.extension.messaging.activemq.deployment. > MessagingXmlParsingDeploymentUnitProcessor.deploy( > MessagingXmlParsingDeploymentUnitProcessor.java:89) ... 6 more > 15:54:11,627 INFO [org.keycloak.services.resources.KeycloakApplication] > (ServerService Thread Pool -- 76) Load config from > vfs:/D:/jboss-wildfly-10.1.0/bin/content/unifiedpush-auth- > server.war/WEB-INF/classes/META-INF/keycloak-server.json 15:54:11,988 > ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 76) > MSC000001: Failed to start service jboss.undertow.deployment. > default-server.default-host./auth: org.jboss.msc.service.StartException > in service jboss.undertow.deployment.default-server.default-host./auth: > java.lang.RuntimeException: RESTEASY003325: Failed to construct public > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax. > servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) at > org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1. > run(UndertowDeploymentService.java:85) at java.util.concurrent. > Executors$RunnableAdapter.call(Executors.java:511) at > java.util.concurrent.FutureTask.run(FutureTask.java:266) at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct > public org.jboss.aerogear.unifiedpush.keycloak. > UpsKeycloakApplication(javax.servlet.ServletContext,org. > jboss.resteasy.core.Dispatcher) at org.jboss.resteasy.core. > ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:162) at > org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance( > ResteasyProviderFactory.java:2246) at org.jboss.resteasy.spi. > ResteasyDeployment.createApplication(ResteasyDeployment.java:304) at > org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:245) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher. > init(ServletContainerDispatcher.java:113) at org.jboss.resteasy.plugins. > server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) > at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed( > LifecyleInterceptorInvocation.java:117) at org.wildfly.extension. > undertow.security.RunAsLifecycleInterceptor.init( > RunAsLifecycleInterceptor.java:78) at io.undertow.servlet.core. > LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) > at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250) > at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133) > at io.undertow.servlet.core.DeploymentManagerImpl$2.call( > DeploymentManagerImpl.java:546) at io.undertow.servlet.core. > DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517) at > io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call( > ServletRequestContextThreadSetupAction.java:42) at > io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call( > ContextClassLoaderSetupAction.java:43) at io.undertow.servlet.api. > LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call( > LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api. > LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call( > LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api. > LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call( > LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.core. > DeploymentManagerImpl.start(DeploymentManagerImpl.java:559) at > org.wildfly.extension.undertow.deployment.UndertowDeploymentService. > startContext(UndertowDeploymentService.java:101) at org.wildfly.extension. > undertow.deployment.UndertowDeploymentService$1. > run(UndertowDeploymentService.java:82) ... 6 more Caused by: > java.lang.RuntimeException: Failed to connect to database at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa > ctory.getConnection(DefaultJpaConnectionProviderFactory.java:184) at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit( > DefaultJpaConnectionProviderFactory.java:130) at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create( > DefaultJpaConnectionProviderFactory.java:35) at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create( > DefaultJpaConnectionProviderFactory.java:25) at org.keycloak.services. > DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99) at > org.keycloak.models.jpa.JpaRealmProviderFactory.create( > JpaRealmProviderFactory.java:34) at org.keycloak.models.jpa. > JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:16) at > org.keycloak.services.DefaultKeycloakSession.getProvider( > DefaultKeycloakSession.java:99) at org.keycloak.models.cache. > DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:70) > at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm( > DefaultCacheRealmProvider.java:163) at org.keycloak.services. > managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:40) at > org.keycloak.services.managers.ApplianceBootstrap. > bootstrap(ApplianceBootstrap.java:31) at org.keycloak.services. > resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:157) > at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication. > setupDefaultRealm(UpsKeycloakApplication.java:40) at > org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:87) > at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.( > UpsKeycloakApplication.java:35) at sun.reflect. > NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect. > NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( > DelegatingConstructorAccessorImpl.java:45) at > java.lang.reflect.Constructor.newInstance(Constructor.java:408) at > org.jboss.resteasy.core.ConstructorInjectorImpl.construct( > ConstructorInjectorImpl.java:150) ... 29 more Caused by: javax.naming.NameNotFoundException: > datasources/KeycloakDS -- service jboss.naming.context.java.jboss.datasources.KeycloakDS > at org.jboss.as.naming.ServiceBasedNamingStore.lookup( > ServiceBasedNamingStore.java:106) at org.jboss.as.naming. > NamingContext.lookup(NamingContext.java:207) at org.jboss.as.naming. > NamingContext.lookup(NamingContext.java:184) at org.jboss.as.naming. > InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) at > org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) at > org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) at > javax.naming.InitialContext.lookup(InitialContext.java:417) at > javax.naming.InitialContext.lookup(InitialContext.java:417) at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa > ctory.getConnection(DefaultJpaConnectionProviderFactory.java:177) ... 49 > more 15:54:11,994 ERROR [org.jboss.as.controller.management-operation] > (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - > address: ([("deployment" => "unifiedpush-auth-server.war")]) - failure > description: { "WFLYCTL0080: Failed services" => > {"jboss.undertow.deployment.default-server.default-host./auth" => > "org.jboss.msc.service.StartException in service > jboss.undertow.deployment.default-server.default-host./auth: > java.lang.RuntimeException: RESTEASY003325: Failed to construct public > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax. > servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) Caused by: > java.lang.RuntimeException: RESTEASY003325: Failed to construct public > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax. > servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) Caused by: > java.lang.RuntimeException: Failed to connect to database Caused by: > javax.naming.NameNotFoundException: datasources/KeycloakDS -- service > jboss.naming.context.java.jboss.datasources.KeycloakDS"}, "WFLYCTL0412: > Required services that are not installed:" => ["jboss.undertow.deployment. > default-server.default-host./auth"], "WFLYCTL0180: Services with > missing/unavailable dependencies" => undefined } 15:54:11,994 ERROR > [org.jboss.as.controller.management-operation] (DeploymentScanner-threads > - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => > "unifiedpush-server-wildfly.war")]) - failure description: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\" > unifiedpush-server-wildfly.war\".PARSE" => "org.jboss.msc.service.StartException > in service jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE: > WFLYSRV0153: Failed to process phase PARSE of deployment > \"unifiedpush-server-wildfly.war\" Caused by: org.jboss.as.server. > deployment.DeploymentUnitProcessingException: WFLYMSGAMQ0055: Could not > parse file D:\\jboss-wildfly-10.1.0\\standalone\\tmp\\vfs\\temp\\ > temp46e687319f527ed3\\content-a52cb55da5bbb09d\\WEB-INF\\hornetq-jms.xml > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: > WFLYMSGAMQ0055: Could not parse file D:\\jboss-wildfly-10.1.0\\ > standalone\\tmp\\vfs\\temp\\temp46e687319f527ed3\\content- > a52cb55da5bbb09d\\WEB-INF\\hornetq-jms.xml Caused by: javax.xml.stream.XMLStreamException: > ParseError at [row,col]:[20,1] Message: Unexpected element > '{urn:jboss:messaging-deployment:1.0}messaging-deployment'"}, > "WFLYCTL0412: Required services that are not installed:" => > ["jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > } 15:54:12,053 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) > WFLYSRV0010: Deployed "unifiedpush-server-wildfly.war" (runtime-name : > "unifiedpush-server-wildfly.war") 15:54:12,053 INFO [org.jboss.as.server] > (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed > "unifiedpush-auth-server.war" (runtime-name : > "unifiedpush-auth-server.war") 15:54:12,053 INFO [org.jboss.as.controller] > (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.unit." > unifiedpush-server-wildfly.war".PARSE: org.jboss.msc.service.StartException > in service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: > WFLYSRV0153: Failed to process phase PARSE of deployment > "unifiedpush-server-wildfly.war" service jboss.undertow.deployment. > default-server.default-host./auth: org.jboss.msc.service.StartException > in service jboss.undertow.deployment.default-server.default-host./auth: > java.lang.RuntimeException: RESTEASY003325: Failed to construct public > org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax. > servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) > ------------------------------ > View this message in context: Failed to process phase PARSE of deployment > ?unifiedpush-server-wildfly.war? > > 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/20160926/3a37aa50/attachment-0001.html From sachidananda.patra at hp.com Mon Sep 26 04:57:17 2016 From: sachidananda.patra at hp.com (Sachidananda Patra) Date: Mon, 26 Sep 2016 01:57:17 -0700 (MST) Subject: [Aerogear-users] =?utf-8?q?Failed_to_process_phase_PARSE_of_deplo?= =?utf-8?q?yment_=E2=80=9Cunifiedpush-server-wildfly=2Ewar=E2=80=9D?= In-Reply-To: References: <1474534304792-902.post@n5.nabble.com> Message-ID: <1474880237047-904.post@n5.nabble.com> I have tried with jboss-wildfly-10.1.0 with aerogear-unifiedpush-server-1.1.3.Final-dist. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902p904.html Sent from the aerogear-users mailing list archive at Nabble.com. From matzew at apache.org Mon Sep 26 05:03:36 2016 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 26 Sep 2016 11:03:36 +0200 Subject: [Aerogear-users] =?utf-8?q?Failed_to_process_phase_PARSE_of_deplo?= =?utf-8?q?yment_=E2=80=9Cunifiedpush-server-wildfly=2Ewar=E2=80=9D?= In-Reply-To: <1474880237047-904.post@n5.nabble.com> References: <1474534304792-902.post@n5.nabble.com> <1474880237047-904.post@n5.nabble.com> Message-ID: Hello, this is the change, that makes it incompatible: https://github.com/aerogear/aerogear-unifiedpush-server/commit/bb1a086427511139201b7b2df06adb9a89c37d33 Background: WF10 comes with a new/different JMS component, hence our JMS config had to change for WF 10.x. Since this change is, unfortunately, not backwards compatible, we went for 1.2.0 line updates only. That said, perhaps you can tweak the above changes into your own fork, and do a manual build? On the other hand, the 1.2.0 line is alpha, yes. but it's really same as 1.1.x, but some more changes for being modern (e.g. WF10, Java8 etc) -M On Mon, Sep 26, 2016 at 10:57 AM, Sachidananda Patra < sachidananda.patra at hp.com> wrote: > I have tried with jboss-wildfly-10.1.0 with > aerogear-unifiedpush-server-1.1.3.Final-dist. > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Failed-to-process-phase-PARSE-of- > deployment-unifiedpush-server-wildfly-war-tp902p904.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/20160926/22998323/attachment.html From sachidananda.patra at hp.com Mon Sep 26 05:12:40 2016 From: sachidananda.patra at hp.com (Sachidananda Patra) Date: Mon, 26 Sep 2016 02:12:40 -0700 (MST) Subject: [Aerogear-users] =?utf-8?q?Failed_to_process_phase_PARSE_of_deplo?= =?utf-8?q?yment_=E2=80=9Cunifiedpush-server-wildfly=2Ewar=E2=80=9D?= In-Reply-To: References: <1474534304792-902.post@n5.nabble.com> <1474880237047-904.post@n5.nabble.com> Message-ID: <1474881160321-906.post@n5.nabble.com> Okay thanks for the update, So I shold use jboss-wildfly-10.1.0 with aerogear-unifiedpush-server-1.2.0.Final-dist, right ? I have tried with wildfly-9.0.1.Final with aerogear-unifiedpush-server-1.1.0.Final-dist, i got below error, while deployed unifiedpush-auth-server.war and unifiedpush-server-wildfly.war unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct public org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher) at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:162) at org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2246) at org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:304) at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:245) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:113) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117) at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78) at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250) at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133) at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:546) at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:559) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) ... 6 more Caused by: java.lang.RuntimeException: Failed to connect to database at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:184) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:35) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:25) at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99) at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:34) at org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:16) at org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99) at org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:70) at org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:163) at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:40) at org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:31) at org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:157) at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40) at org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:87) at org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.(UpsKeycloakApplication.java:35) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:150) ... 29 more Caused by: javax.naming.NameNotFoundException: datasources/KeycloakDS -- service jboss.naming.context.java.jboss.datasources.KeycloakDS at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) at javax.naming.InitialContext.lookup(InitialContext.java:417) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:177) ... 49 more -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902p906.html Sent from the aerogear-users mailing list archive at Nabble.com. From sachidananda.patra at hp.com Mon Sep 26 05:24:23 2016 From: sachidananda.patra at hp.com (Sachidananda Patra) Date: Mon, 26 Sep 2016 02:24:23 -0700 (MST) Subject: [Aerogear-users] =?utf-8?q?Failed_to_process_phase_PARSE_of_deplo?= =?utf-8?q?yment_=E2=80=9Cunifiedpush-server-wildfly=2Ewar=E2=80=9D?= In-Reply-To: References: <1474534304792-902.post@n5.nabble.com> <1474880237047-904.post@n5.nabble.com> Message-ID: <378fd380695b465b9f69ad4bde055d62@G1W8600.auth.hpicorp.net> Hi Matthias, I would like to know the Environment setup for Configuring Aerogear UPS after following the https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation? Which is posted here http://aerogear-users.1116366.n5.nabble.com/Unified-push-server-development-environment-setup-td7.html , I would like to know configuration procedure stepwise, where I can debug the app server through break points. Thanks, Sachidananda From: Matthias Wessendorf [via aerogear-users] [mailto:ml-node+s1116366n905h82 at n5.nabble.com] Sent: Monday, September 26, 2016 2:35 PM To: Patra, Sachidananda (TCS S&CO Platform Team (L2/L3)) Subject: Re: [Aerogear-users] Failed to process phase PARSE of deployment ?unifiedpush-server-wildfly.war? Hello, this is the change, that makes it incompatible: https://github.com/aerogear/aerogear-unifiedpush-server/commit/bb1a086427511139201b7b2df06adb9a89c37d33 Background: WF10 comes with a new/different JMS component, hence our JMS config had to change for WF 10.x. Since this change is, unfortunately, not backwards compatible, we went for 1.2.0 line updates only. That said, perhaps you can tweak the above changes into your own fork, and do a manual build? On the other hand, the 1.2.0 line is alpha, yes. but it's really same as 1.1.x, but some more changes for being modern (e.g. WF10, Java8 etc) -M On Mon, Sep 26, 2016 at 10:57 AM, Sachidananda Patra <[hidden email]> wrote: I have tried with jboss-wildfly-10.1.0 with aerogear-unifiedpush-server-1.1.3.Final-dist. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902p904.html Sent from the aerogear-users mailing list archive at Nabble.com. _______________________________________________ Aerogear-users mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/aerogear-users -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ twitter: http://twitter.com/mwessendorf _______________________________________________ Aerogear-users mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/aerogear-users ________________________________ If you reply to this email, your message will be added to the discussion below: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902p905.html To unsubscribe from Failed to process phase PARSE of deployment ?unifiedpush-server-wildfly.war?, click here. NAML -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE-of-deployment-unifiedpush-server-wildfly-war-tp902p907.html Sent from the aerogear-users mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160926/af9ef729/attachment-0001.html From sachidananda.patra at hp.com Mon Sep 26 05:29:54 2016 From: sachidananda.patra at hp.com (Sachidananda Patra) Date: Mon, 26 Sep 2016 02:29:54 -0700 (MST) Subject: [Aerogear-users] Unified push server development environment setup In-Reply-To: References: <1429625792522-7.post@n5.nabble.com> Message-ID: <1474882194943-908.post@n5.nabble.com> After running the server having followed https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation what are the steps to Import unifed-push server code to eclipse / intellij IDEA and configure the server, so that i can browse the code, set the breakpoints and debug. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unified-push-server-development-environment-setup-tp7p908.html Sent from the aerogear-users mailing list archive at Nabble.com.