AeroGear unified push notification
by Walto, David
Hi, I a new AeroGear unified push notification user. I am trying to create a simple push notification from a WebSphere java application.
I have created a couple of push notification classes to test (below) and both version I get the error:
SenderClient E Send did not succeed: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 64
I have the following jars for this application.
[cid:image001.png@01D0EB25.5E1F6EE0]
[cid:image003.png@01D0EB25.C89EC4F0]
Any direction how to resolve this would be greatly appreciated.
Thanks in advance.
David Walto
Senior Application Engineer | EMR Engineering and Integration
Baystate Health | Information & Technology
1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: 413-794-5570
----------------------------------------------------------------------
Please view our annual report at http://baystatehealth.org/annualreport
CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at http://baystatehealth.org.
9 years, 1 month
Unified push server development environment setup
by mo
Hi,
I'm trying to run the unified push server in a development environment to
troubleshoot and understand it better. I'm wondering if there is any
documentation available to assist me with setting up development environment
for it. I've looked though documents under "Contributing to AeroGear", but
I am in need of a more detailed guide. I'd like to get to a point where I
can run unified push, break point, and inspect variables, and so on.
So far I've managed to run 'mvn test' successfully on the unified push
server source code. I use Eclipse, so I wanted to import the project. I
get quite a lot of errors in doing so.
I am troubleshooting version 1.0.2. We use OpenShift to deploy the aerogear
server.
I appreciate any help. Thank you.
Michi Oshima
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unified-push-server-developme...
Sent from the aerogear-users mailing list archive at Nabble.com.
10 years
categories have been hijacked
by Kelvin Lunsford
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.
New features should get new names and new commands.
- Kelvin
10 years
AeroGear UnifiedPush Server Java Client Send Emoji
by redprogrammer
Hi,
i am using AeroGear UnifiedPush Server on openshift cartige. İ hava a
problem while using java client. I want to send emojis in push notifications
but i can't send emojis. This error throwed
Jun 24, 2016 7:57:46 PM org.jboss.aerogear.unifiedpush.DefaultPushSender
submitPayload
INFO: HTTP Response code from UnifiedPush Server: 500
Jun 24, 2016 7:57:47 PM org.jboss.aerogear.unifiedpush.DefaultPushSender
submitPayload
SEVERE: The Unified Push Server returned status code: 500
Exception in thread "main"
org.jboss.aerogear.unifiedpush.exception.PushSenderHttpException
at
org.jboss.aerogear.unifiedpush.DefaultPushSender.submitPayload(DefaultPushSender.java:281)
at
org.jboss.aerogear.unifiedpush.DefaultPushSender.send(DefaultPushSender.java:230)
at com.ratemyapp.pushtest.NewClass.main(NewClass.java:44)
Can you help me??
Best Regards
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/AeroGear-UnifiedPush-Server-J...
Sent from the aerogear-users mailing list archive at Nabble.com.
10 years, 3 months
Enabled TLS 1.2
by Ramona.Cristea
Hello,
We would like for our push server to support only TLS 1.2 connections for
security reasons.
The Android documentation for SSLSocket says that TLS 1.1 and TLS 1.2 is
supported within android starting API level 16+ (Android 4.1, Jelly Bean).
But it is by default disabled but starting with API level 20+ (Android 4.4
for watch, Kitkat Watch and Android 5.0 for phone, Lollipop) they are
enabled.
We set the minimum sdk version to API 16, but we would like to know if the
Aero Gear library enables TLS 1.2 protocol when doing a connection?
If not, then all connections on smartphones with android versions < 5.0 will
fail.
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Enabled-TLS-1-2-tp707.html
Sent from the aerogear-users mailing list archive at Nabble.com.
10 years, 3 months
Re: [Aerogear-users] [aerogear-dev] AeroGear Cordova release
by Erik Jan de Wit
Hi,
We are going to release another version of the aerogear push plugin, as
always I've created a branch for you to test. The biggest change it the use
of FCM for google so be sure to test it against a compatible UPS.
Add the plugin with the following command:
$> cordova plugin add
https://github.com/aerogear/aerogear-cordova-push.git\#release-3.0.0
Other changes are:
[image: Major] [image: Bug] AGCORDOVA-133
<https://issues.jboss.org/browse/AGCORDOVA-133> Library Dependencies
Conflict With Every Other Plugin Requiring The Same
<https://issues.jboss.org/browse/AGCORDOVA-133>
[image: Major] [image: Tracker] AGCORDOVA-134
<https://issues.jboss.org/browse/AGCORDOVA-134> geting problem in cordova
build <https://issues.jboss.org/browse/AGCORDOVA-134>
[image: Major] [image: Feature Request] AGCORDOVA-138
<https://issues.jboss.org/browse/AGCORDOVA-138> Update Cordova-Android to
use AGDROID 3.0.0 for GCM and InstanceID
<https://issues.jboss.org/browse/AGCORDOVA-138>
[image: Major] [image: Task] AGCORDOVA-140
<https://issues.jboss.org/browse/AGCORDOVA-140> AeroGear Cookbook Updates
<https://issues.jboss.org/browse/AGCORDOVA-140>
[image: Major] [image: Sub-task] AGCORDOVA-141
<https://issues.jboss.org/browse/AGCORDOVA-141> Push Hello World update
<https://issues.jboss.org/browse/AGCORDOVA-141>
[image: Major] [image: Feature Request] AGCORDOVA-145
<https://issues.jboss.org/browse/AGCORDOVA-145> Update Cordova-Android to
use FCM enabled AGDroid <https://issues.jboss.org/browse/AGCORDOVA-145>
On Fri, Jun 17, 2016 at 10:49 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
> cool!
>
> On Thu, Jun 16, 2016 at 9:01 PM, Erik Jan de Wit <edewit(a)redhat.com>
> wrote:
>
>> yeah, let's do that
>>
>> On Thu, Jun 16, 2016 at 1:53 PM, Matthias Wessendorf <matzew(a)apache.org>
>> wrote:
>>
>>> Hi Erik,
>>>
>>> now that FCM got merged, can you tag and release the 3.0.0 bits ?
>>>
>>> -Matthias
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> twitter: http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Cheers,
>> Erik Jan
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
Cheers,
Erik Jan
10 years, 3 months
iOS Push issue when having multiple Installations
by Bourillon, Matthias
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :
1. We have 89 installations registered against an iOS Production Variant
2. We send a message
3. No one receive the message on our iOS App
4. We disable ALL installations but 1
5. We send a message
6. The 1 device receives the push notification and works as expected
We have other iOS variants with thousands of registrations working without any problem like this.
Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.
Thanks,
Matthias
10 years, 3 months
Re: [Aerogear-users] iOS Push issue when having multiple Installations
by Javornik, Romain
Hello Matthias,
in regard of the upgrade, we were running the 1.0.2 and we migrate to the 1.1.1, here some problem you might want to be aware of.
The update was smooth from 1.0.2 to 1.0.3, but I have to add the parameter ‘transformedBitIsBoolean’ in our DB connection (standalone.xml).
<connection-url>jdbc:mysql://localhost:3306/unifiedpush?transformedBitIsBoolean=true</connection-url>
But it was quite hard for us to update to 1.1.0 from our 1.0.3, the problem where coming from our DB :
· Redundancy of FK
· Wrong data type
· Wrong data order in the table (even if it shouldn’t matter, it does for some reasons)
· Wrong table name
So basically our database was not in sync with the one the migrator tool expect, specially the part related to the table ‘variant’.
The way we proceed to make the migration is the following :
1. We made some modification in our current database (creation of columns, change columns order in table)
2. We exported the data, and reimport all of it in a fresh 1.0.3 installation
3. We run the migrator tool to 1.1.0
4. We add in variant.VARIANT_TYPE the type of OS (ios, android) wich was missing
The modifications made in the step 1 make the data import in the step 2 possible,
they come from the differences between our schema and the schema from scratch.
Best Regards,
Romain
De : Bourillon, Matthias
Envoyé : mercredi 15 juin 2016 11:45
À : Javornik, Romain
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations
Fait un reply là-dessus sur la liste aerogear-users(a)lists.jboss.org<mailto:aerogear-users@lists.jboss.org>
De : aerogear-users-bounces(a)lists.jboss.org<mailto:aerogear-users-bounces@lists.jboss.org> [mailto:aerogear-users-bounces@lists.jboss.org] De la part de Matthias Wessendorf
Envoyé : mardi 7 juin 2016 10:13
À : aerogear-users(a)lists.jboss.org<mailto:aerogear-users@lists.jboss.org>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations
On Tuesday, 7 June 2016, Bourillon, Matthias <Matthias.Bourillon(a)saint-gobain.com<mailto:Matthias.Bourillon@saint-gobain.com>> wrote:
Hello Matthias,
We are still in 1.0.0 as 1.1.0 migration process fails with our instance.
hrm, any pointers?
To me, invalid tokens have been added on the server due to App development process during which App with development provisioning profile have registered against the server.
yes!
Please note, dev/prod variant settings should not be mixed, for different reasons
If I understand correctly, in 1.1.0, if we have Dev token registered against the server they’ll be discovered invalid by Aerogear server and message sending will not be impacted. Is this right?
Thanks,
Matthias
De : aerogear-users-bounces(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces(a)lists.jboss.org');> [mailto:aerogear-users-bounces@lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces(a)lists.jboss.org');>] De la part de Matthias Wessendorf
Envoyé : lundi 6 juin 2016 21:17
À : aerogear-users(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users(a)lists.jboss.org');>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations
are you using the 1.1.0 ?
I think it should not stop.
Question: how did invalid tokens end up at the server?
On Mon, Jun 6, 2016 at 4:56 PM, Bourillon, Matthias <Matthias.Bourillon(a)saint-gobain.com<javascript:_e(%7B%7D,'cvml','Matthias.Bourillon(a)saint-gobain.com');>> wrote:
Matthias,
I wanted to validate this behavior and I just created a script, manually sending a Payload to Apple Push service, 1 by 1 to our 89 installations.
I am getting the same behavior : as soon as a payload is being sent to an invalid token, remaining payloads are not sent to devices. Is this something Apple block on their side?
Thanks,
Matthias
De : aerogear-users-bounces(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces(a)lists.jboss.org');> [mailto:aerogear-users-bounces@lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces(a)lists.jboss.org');>] De la part de Matthias Wessendorf
Envoyé : lundi 6 juin 2016 12:40
À : aerogear-users(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users(a)lists.jboss.org');>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations
I think yes, the problem was the a mix of tokens for different profiles (e.g. dev vs. prod)
-M
On Mon, Jun 6, 2016 at 11:32 AM, Bourillon, Matthias <Matthias.Bourillon(a)saint-gobain.com<javascript:_e(%7B%7D,'cvml','Matthias.Bourillon(a)saint-gobain.com');>> wrote:
Matthias,
Does the behaviour I described makes sense?
In 1.0.0, if one of the token is invalid, can it block the whole push sending to other tokens?
Matthias
De : aerogear-users-bounces(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces(a)lists.jboss.org');> [mailto:aerogear-users-bounces@lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users-bounces(a)lists.jboss.org');>] De la part de Matthias Wessendorf
Envoyé : lundi 6 juin 2016 11:20
À : aerogear-users(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','aerogear-users(a)lists.jboss.org');>
Objet : Re: [Aerogear-users] iOS Push issue when having multiple Installations
Hi,
I think you are hitting a a bug. in the 1.1.0 series we did add a catch for reported invalid tokens:
https://github.com/aerogear/aerogear-unifiedpush-server/commit/a44773a8db...
-Matthias
On Mon, Jun 6, 2016 at 11:14 AM, Bourillon, Matthias <Matthias.Bourillon(a)saint-gobain.com<javascript:_e(%7B%7D,'cvml','Matthias.Bourillon(a)saint-gobain.com');>> wrote:
Hello,
We are facing an issue while using Aerogear Push Server with an iOS variant.
Here is the scenario :
1. We have 89 installations registered against an iOS Production Variant
2. We send a message
3. No one receive the message on our iOS App
4. We disable ALL installations but 1
5. We send a message
6. The 1 device receives the push notification and works as expected
We have other iOS variants with thousands of registrations working without any problem like this.
Can the number of registered device impact the sending behavior? Can a wrong token or anything else block the notification sending to Apple? Logs do not seem to complain about any particular issue.
We are using Aerogear Push Server 1.0.0.
Thanks,
Matthias
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','Aerogear-users(a)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(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','Aerogear-users(a)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(a)lists.jboss.org<javascript:_e(%7B%7D,'cvml','Aerogear-users(a)lists.jboss.org');>
https://lists.jboss.org/mailman/listinfo/aerogear-users
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
--
Sent from Gmail Mobile
10 years, 3 months
Aerogear Push Notification in iOS
by Raghavendra
Hi,
I am implementing Push Notification on Android and iOS
My code works perfectly fine in Android. However, for iOS, i get the below
error on JBOSS server.
12:15:21,457 INFO [APNsPushNotificationSender] (Thread-37
(HornetQ-client-global-threads-949943370)) One batch to APNs has been
submitted
12:15:21,716 INFO [APNsPushNotificationSender] (MonitoringThread-1)
Removing invalid token:
8c21b00e4f2258a0bd852fedaca8b3507a326e365465ae621dbed5418806f2ce
I am not sure what mistake i am making.
Please help.
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-Push-Notification-in...
Sent from the aerogear-users mailing list archive at Nabble.com.
10 years, 3 months
SSL issue at Amazon EC2 With aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8
by mridul
Hi,
I am successfully running a test for
aerogear-unifiedpush-server-1.2.0-alpha.1 on Wildfly 10 , Java 8 in my
office network with perfect access , registration of devices and messaging
by using https://my_pub_ip:8443/ag-push. So far so good, now last Monday I
set up the same environment (for production purposes) at Amazone EC2
instance and tested it with Self signed keys. I am able to access
https://amazone_pub_ip:8443 , it displays me the wildfly index page. The
moment I access /ag-push in amazone ec2 instance I get a run time exception
as below :
18:16:20,702 ERROR [io.undertow.request] (default task-22) UT005023:
Exception handling request to /ag-push/: java.lang.RuntimeException: Unable
to resolve realm public key remotely
at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:136)
at
org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:85)
at
org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:74)
at
org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:50)
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:284)
at
io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263)
at
io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
at
io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793)
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: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
at
org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
at
org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
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:107)
Please share some insight to this issue
Thanks.
Mridul.
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/SSL-issue-at-Amazon-EC2-With-...
Sent from the aerogear-users mailing list archive at Nabble.com.
10 years, 3 months
