October 2017 - Aerogear-users - Jboss List Archives

by Javornik, Romain

Hello, We are currently running Aerogear Push 1.1.1.Final on a Jboss EAP 6.4 since a year now without any issues. However, a problem that we had prior 1.1.0 release (http://lists.jboss.org/pipermail/aerogear-users/2016-June/000821.html) is coming back. When we are making a push we got this error (sometimes) : 08:29:08,265 WARNING [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Internal cache size exceeded, new size is: 150 08:29:08,265 SEVERE [org.jboss.aerogear.unifiedpush.message.sender.APNsPushNotificationSender] (MonitoringThread-1) Error sending payload to APNs server: com.notnoop.exceptions.ApnsDeliveryErrorException: Failed to deliver notification with error code 8 at com.notnoop.apns.internal.ApnsConnectionImpl$2.run(ApnsConnectionImpl.java:199) [apns-1.0.0.Beta6.jar:] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] Do you know where the problem might come from ? Best Regards, Romain Javornik

6 years, 11 months

3
7
0 / 0

AeroGear Android Offline

by Daniel Passos

A long time ago we try to draft an offline library, we have created an aerogear-android-offline GH repo, but we did not work too much on it there and never released it. Should we delete this repo or only add a notice on the README -- -- Passos

7 years

2
2
0 / 0

AeroGear Sync Maintain

by Daniel Passos

Hi We are not investing time on AeroGear Sync for a long time and now we are working in a Sync feature for Feedhenry Sync. Should we deprecate it and add a notice on the README repos? -- -- Passos

7 years

2
1
0 / 0

AeroGear Digger - installation and E2E app building demo

by Ali Ok

Hello, I would like to share this demo video of AeroGear Digger with you: https://youtu.be/DxPgJcD6KSY It basically shows everything you need to kick start AeroGear Digger: - Starting up an OpenShift cluster to install AeroGear Digger on it - Installing a AeroGear Digger instance from scratch - Building a sample application and installing it on a device - Using AeroGear Digger CLI Instructions used in the demo video is available in the README file in the repository: https://github.com/aerogear/digger-jenkins Thanks Laura Fitzgerald for the nice voice over! Greetings, Ali

7 years

4
7
0 / 0

DB Migration failing (1.1.3 to 1.2.0)

by Yoann Archambault

Hello, I'm trying to upgrade to 1.2.0 so i cloned our production database and am trying to run the ups-migrator but i'm getting a strange error about one of the new tables. I'm running a postgresql 9.6 database on centos 6.9 and wildfly 10.1 I'm attaching the full output of the migrator (.txt) as well as the contents of my changelog table (.xls) Any help getting unstuck would be greatly appreciated! Yoann Archambault ---- DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-16::matzew (generated): Computed checksum for addPrimaryKey:[ columnNames="id" constraintName="PRIMARY" tableName="flat_push_message_info" ] as 3464de402322ecb56aa2ec149c55bd6d DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-16::matzew (generated): Computed checksum for 7:3464de402322ecb56aa2ec149c55bd6d: as d120fdfbd02d16d8f644519467ff5b87 DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Running Changeset:liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated) DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Changeset liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated) DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Reading ChangeSet: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated) DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Executing Statement: liquibase.statement.core.AddPrimaryKeyStatement@54eb2b70 DEBUG 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Executing EXECUTE database command: ALTER TABLE public.variant_error_status ADD CONSTRAINT "PRIMARY" PRIMARY KEY (push_message_variant_id) SEVERE 10/16/17 2:43 PM: liquibase: liquibase/master.xml: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Change Set liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated) failed. Error: org.postgresql.util.PSQLException: ERROR: relation "PRIMARY" already exists liquibase.exception.DatabaseException: org.postgresql.util.PSQLException: ERROR: relation "PRIMARY" already exists at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:316) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:55) at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:122) at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1227) at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1210) at liquibase.changelog.ChangeSet.execute(ChangeSet.java:550) at liquibase.changelog.visitor.UpdateVisitor.visit(UpdateVisitor.java:43) at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:73) at liquibase.Liquibase.update(Liquibase.java:200) at liquibase.integration.commandline.Main.doMigration(Main.java:1044) at liquibase.integration.commandline.Main.run(Main.java:175) at liquibase.integration.commandline.Main.main(Main.java:94) Caused by: org.postgresql.util.PSQLException: ERROR: relation "PRIMARY" already exists at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:395) at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:314) ... 11 more DEBUG 10/16/17 2:43 PM: liquibase: liquibase/1.2.0/2017-09-06-flat-model-entities.xml::1504688114371-22::matzew (generated): Release Database Lock

7 years, 1 month

1
0
0 / 0

AeroGear Digger Logo

by Ali Ok

Hello, We would like to pick a logo for the new AeroGear module, Digger [1]. James Cobb has already prepared some great designs and now we vote to pick the best one [2]. We have prepared a Google poll (no login required) here: https://goo.gl/forms/WdUoHecQtrshMkBg1 The poll will be open for 10 days (until June 29th 10:00 AM UTC). [1] : https://github.com/aerogear/digger-jenkins [2] : https://issues.jboss.org/browse/DESIGN-943 Cheers, Ali

7 years, 1 month

4
4
0 / 0

Re: [Aerogear-users] Is Jboss EAP 6.4.0 GA still supported by Aerogear UPS?

by jeff01

I filed a related Jira request here: https://issues.jboss.org/browse/AEROGEAR-1759 -- Sent from: http://aerogear-users.1116366.n5.nabble.com/

7 years, 1 month

2
5
0 / 0

Error when deploying Aerogear UPS 1.2.--Final .war into Jboss EAP7: Illegal character in path at index 1: ${ups.auth.server.url}

by jeff01

Hi, I followed the instructions at https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-install.... I am close to get ag-push (Aerogear UPS 1.2.0-Final) deployed, but it threw the following error: "{\"WFLYCTL0080: Failed services\" => {\"jboss.undertow.deployment.default-server.default-host./ag-push\" => \"org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./ag-push: java.lang.IllegalArgumentException: Illegal character in path at index 1: ${ups.auth.server.url} Caused by: java.lang.IllegalArgumentException: Illegal character in path at index 1: ${ups.auth.server.url} Caused by: java.net.URISyntaxException: Illegal character in path at index 1: ${ups.auth.server.url}\"}}" What does this mean? Should I download auth-server war file (keycloak) somewhere first? The servers folder in 1.1.x used to have a auth-server war file, but NOT in 1.2.0-Final distribution bundle. So where should I download this auth-server war file and what version? Any online documentation mentions that? Thank you. -- Sent from: http://aerogear-users.1116366.n5.nabble.com/

7 years, 1 month

2
1
0 / 0

aerogear-ios-push 3.0.0 for Swift 4 and aerogear-ios-push-objc 2.0.0 released

by Julio Cesar Sanchez Hernandez

Hi, We have updated aerogear-ios-push to Swift 4 and it has been released in CocoaPods as AeroGearPush-Swift 3.0.0. We have moved the Objective-C version to a new repo and also released it as AeroGearPush 2.0.0. Both of them drop support for iOS 8. Notice that the names have been changed for consistency with our other libs, so you will have to edit your podfiles from pod 'AeroGear-Push-Swift' to pod 'AeroGearPush-Swift' and pod 'AeroGear-Push' to pod 'AeroGearPush' Searching on CocoaPods website will show the old ones deprecated in favour of the new ones.

7 years, 1 month

1
0
0 / 0

iOS 11 Support

by Philipp Koetz, mVISE AG

Dear Aerogear Team, does the 1.2 release works fine for iOS 11? We have right now the problem that messages will be rejected if there is an alert, badge or sound key in the message. In the current version of Aerogear push server we are using (1.1.3) is the alert key everytime attached to the messages json. Regards, Philipp Koetz

7 years, 1 month

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Aerogear-users October 2017