Aearogear with Android SDK on OpenShift: Default FirebaseApp is not initialized
by Robert Baumgartner
Hi Gurus,
I tried to use AeroGear and run into a little problem...
I installes Aerogear on OpenShift/Minishift incl Kerberos, like
https://github.com/aerogear/aerogear-unifiedpush-server/
After that I used the guide at:
https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/
Then I got a complier error when I tried to run the PushApplication
Error:(25, 23) error: TAG has private access in FragmentActivity
I tried to fixed this in
MainActivity.java by adding a
private static final String TAG = MainActivity.class.getSimpleName();
So I got the following error at application runtime:
W/System: ClassLoader referenced unknown path:
/data/app/com.push.pushapplication-1/lib/arm64
I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
I/InstantRun: starting instant run server: is main process
W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
android.support.graphics.drawable.VectorDrawableCompat.updat
eTintFilter(android.graphics.PorterDuffColorFilter,
android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would
have incorrectly overridden the package-private method in
android.graphics.drawable.Drawable
E/MainActivity: *Default FirebaseApp is not initialized in this process
com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.*
java.lang.IllegalStateException: Default FirebaseApp is not
initialized in this process com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.
at com.google.firebase.FirebaseApp.getInstance(Unknown
Source)
at com.google.firebase.iid.Fireba
seInstanceId.getInstance(Unknown Source)
at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:
100)
at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:
96)
at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
earFCMPushRegistrar.java:145)
at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
earFCMPushRegistrar.java:135)
at android.os.AsyncTask$2.call(AsyncTask.java:305)
at java.util.concurrent.FutureTas
k.run(FutureTask.java:237)
at android.os.AsyncTask$SerialExe
cutor$1.run(AsyncTask.java:243)
at java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
I could not find any workaroud. Any tip/solution wolcome?
Lg Robert
Mit freundlichen Grüßen / Kind regards
Robert Baumgartner
Senior Solution Architect Middleware
Red Hat Austria GmbH <https://www.redhat.com>
Millenniumtower 24.Stock
Handelskai 94-96
A-1200 Wien
robert.baumgartner(a)redhat.com M: +43-660-5913883
<https://red.ht/sig>
6 years, 1 month
Aearogear with Android SDk on OpenShift
by Robert Baumgartner
Hi Gurus,
I tried to use AeroGear and run into a little problem...
I installes Aerogear on OpenShift/Minishift incl Kerberos, like
https://github.com/aerogear/aerogear-unifiedpush-server/
After that I used the guide at:
https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/
Then I got a complier error when I tried to run the PushApplication
Error:(25, 23) error: TAG has private access in FragmentActivity
I tried to fixed this in
MainActivity.java by adding a
private static final String TAG = MainActivity.class.getSimpleName();
So I got the following error at application runtime:
W/System: ClassLoader referenced unknown path: /data/app/com.push.
pushapplication-1/lib/arm64
I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
I/InstantRun: starting instant run server: is main process
W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
android.support.graphics.drawable.VectorDrawableCompat.
updateTintFilter(android.graphics.PorterDuffColorFilter,
android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would
have incorrectly overridden the package-private method in
android.graphics.drawable.Drawable
E/MainActivity: *Default FirebaseApp is not initialized in this process
com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.*
java.lang.IllegalStateException: Default FirebaseApp is not
initialized in this process com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.
at com.google.firebase.FirebaseApp.getInstance(Unknown
Source)
at
com.google.firebase.iid.FirebaseInstanceId.getInstance(Unknown
Source)
at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:100)
at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:96)
at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$4.doInBackground(AeroGearFCMPushRegistrar.java:145)
at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$4.doInBackground(AeroGearFCMPushRegistrar.java:135)
at android.os.AsyncTask$2.call(AsyncTask.java:305)
at java.util.concurrent.FutureTask.run(FutureTask.
java:237)
at android.os.AsyncTask$SerialExecutor$1.run(
AsyncTask.java:243)
at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
I could not find any workaroud. Any tip/solution wolcome?
Lg Robert
Kind regards
Robert Baumgartner
Senior Solution Architect Middleware
Red Hat Austria GmbH <https://www.redhat.com>
Millenniumtower 24.Stock
Handelskai 94-96
A-1200 Wien
robert.baumgartner(a)redhat.com M: +43-660-5913883
<https://red.ht/sig>
6 years, 1 month
Problems to deliver PushNotification to all configured variants
by Christoph Kettler
Hello AG-Team,
we are currently confrontet with serious problems regarding the delivery of
push messages to variants/devices.
Our system is running Aerogear UnifiedPush Server V1.2.0 on a Wildfly
10.1.0.final.
We have currently 11 Variants in an Application, and are pushing against
this Application. According to the log file (see below), all variants shall
be processed by the server. However, this is not true.
The configuration for "App <-> PushServer (Variant)" and for "PushService
(Google FCM) <-> PushServer" ist valid for each.
We are able to sent a PushNotification directly from the Firebase console to
the app, and also directly from the AeroGear UI using "Send Notification To
This App". The PushNotifications will always be delivered.
Here is a listing from the Logging. You can see in the first line that the
server prepare for 11 Variants, but only 6 are handled:
2018-02-02 12:27:32,862 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Preparing message delivery and
loading tokens for the ANDROID 3rd-party Push Network (for 11 variants)
// push for 11 variants, fits with the configuration in the application
2018-02-02 12:27:32,871 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-4
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 1/11
2018-02-02 12:27:32,871 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-4 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM topic: /topics/1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx
2018-02-02 12:27:32,879 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #1, containing 1
tokens, for android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-10
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 2/11
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #7, containing 25
tokens, for android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-10 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 25 registrationIDs
2018-02-02 12:27:32,915 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-14
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 3/11
2018-02-02 12:27:32,916 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-14 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 9 registrationIDs
2018-02-02 12:27:32,924 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #9, containing 9
tokens, for android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,929 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-12
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 4/11
2018-02-02 12:27:32,929 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-12 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 11 registrationIDs
2018-02-02 12:27:32,931 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #12, containing 11
tokens, for android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,939 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-9
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
//variant no. 5/11
2018-02-02 12:27:32,940 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-9 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 10 registrationIDs
2018-02-02 12:27:32,940 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #14, containing 10
tokens, for android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
2018-02-02 12:27:32,945 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-2
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 6/11
2018-02-02 12:27:32,946 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-2 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 3 registrationIDs
2018-02-02 12:27:32,946 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #16, containing 3
tokens, for android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
// logging ends here
Any known issues on that? Or, is there an "upper limit" for variants within
an application which should not be exceeded and maybe it can be configurated
to scale upwards?
Thanks for any help and feedback.
Best regards,
Chris
--
Sent from: http://aerogear-users.1116366.n5.nabble.com/
6 years, 1 month
Problems to deliver PushNotification to all configured variants
by Christoph Kettler
Hello AG-Team,
we are currently confrontet with serious problems regarding the delivery of
push messages to variants/devices.
Our system is running Aerogear UnifiedPush Server V1.2.0 on a Wildfly
10.1.0.final.
We have currently 11 Variants in an Application, and are pushing against
this Application. According to the log file (see below), all variants shall
be processed by the server. However, this is not true.
The configuration for "App <-> PushServer (Variant)" and for "PushService
(Google FCM) <-> PushServer" ist valid for each.
We are able to sent a PushNotification directly from the Firebase console to
the app, and also directly from the AeroGear UI using "Send Notification To
This App". The PushNotifications will always be delivered.
Here is a listing from the Logging. You can see in the first line that the
server prepare for 11 Variants, but only 6 are handled:
2018-02-02 12:27:32,862 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Preparing message delivery and
loading tokens for the ANDROID 3rd-party Push Network (for 11 variants)
// push for 11 variants, fits with the configuration in the application
2018-02-02 12:27:32,871 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-4
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 1/11
2018-02-02 12:27:32,871 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-4 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM topic: /topics/1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx
2018-02-02 12:27:32,879 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #1, containing 1
tokens, for android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-10
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 2/11
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #7, containing 25
tokens, for android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-10 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 25 registrationIDs
2018-02-02 12:27:32,915 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-14
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 3/11
2018-02-02 12:27:32,916 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-14 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 9 registrationIDs
2018-02-02 12:27:32,924 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #9, containing 9
tokens, for android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,929 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-12
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 4/11
2018-02-02 12:27:32,929 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-12 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 11 registrationIDs
2018-02-02 12:27:32,931 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #12, containing 11
tokens, for android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,939 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-9
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
//variant no. 5/11
2018-02-02 12:27:32,940 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-9 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 10 registrationIDs
2018-02-02 12:27:32,940 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #14, containing 10
tokens, for android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
2018-02-02 12:27:32,945 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-2
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 6/11
2018-02-02 12:27:32,946 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-2 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 3 registrationIDs
2018-02-02 12:27:32,946 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #16, containing 3
tokens, for android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
// logging ends here
Any known issues on that? Or, is there an "upper limit" for variants within
an application which should not be exceeded and maybe it can be configurated
to scale upwards?
Thanks for any help and feedback.
Best regards,
Chris
--
Sent from: http://aerogear-users.1116366.n5.nabble.com/
6 years, 1 month
Problems to deliver PushNotification to all configured variants
by Christoph Kettler
Hello AG-Team,
we are currently confrontet with serious problems regarding the delivery of
push messages to variants/devices.
Our system is running Aerogear UnifiedPush Server V1.2.0 on a Wildfly
10.1.0.final.
We have currently 11 Variants in an Application, and are pushing against
this Application. According to the log file (see below), all variants shall
be processed by the server. However, this is not true.
The configuration for "App <-> PushServer (Variant)" and for "PushService
(Google FCM) <-> PushServer" ist valid for each.
We are able to sent a PushNotification directly from the Firebase console to
the app, and also directly from the AeroGear UI using "Send Notification To
This App". The PushNotifications will always be delivered.
Here is a listing from the Logging. You can see in the first line that the
server prepare for 11 Variants, but only 6 are handled:
2018-02-02 12:27:32,862 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Preparing message delivery and
loading tokens for the ANDROID 3rd-party Push Network (for 11 variants)
// push for 11 variants, fits with the configuration in the application
2018-02-02 12:27:32,871 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-4
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 1/11
2018-02-02 12:27:32,871 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-4 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM topic: /topics/1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx
2018-02-02 12:27:32,879 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #1, containing 1
tokens, for android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-10
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 2/11
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #7, containing 25
tokens, for android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,898 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-10 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 25 registrationIDs
2018-02-02 12:27:32,915 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-14
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 3/11
2018-02-02 12:27:32,916 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-14 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 9 registrationIDs
2018-02-02 12:27:32,924 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #9, containing 9
tokens, for android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,929 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-12
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 4/11
2018-02-02 12:27:32,929 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-12 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 11 registrationIDs
2018-02-02 12:27:32,931 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #12, containing 11
tokens, for android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
2018-02-02 12:27:32,939 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-9
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
//variant no. 5/11
2018-02-02 12:27:32,940 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-9 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 10 registrationIDs
2018-02-02 12:27:32,940 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #14, containing 10
tokens, for android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
2018-02-02 12:27:32,945 INFO
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-2
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 6/11
2018-02-02 12:27:32,946 INFO
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-2 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 3 registrationIDs
2018-02-02 12:27:32,946 INFO
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #16, containing 3
tokens, for android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
// logging ends here
Any known issues on that? Or, is there an "upper limit" for variants within
an application which should not be exceeded and maybe it can be configurated
to scale upwards?
Thanks for any help and feedback.
Best regards,
Chris
--
Sent from: http://aerogear-users.1116366.n5.nabble.com/
6 years, 1 month
JIRA instances: One for the better (or one to rule them all)
by Matthias Wessendorf
Hi folks!
shortly after AeroGear.org project was started, and different technologies
and scopes were added, we started to reflect that with multiple different
JIRA instances. For instance besides the canonical AEROGEAR instance we
have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
(AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
I am proposing to retire all instances and start using only the AEROGEAR
instance.
In Push, we had similar discussion, we had different instances for
simplepush, ups and webpush; For sanity we ended up running all things in
AGPUSH, and using components and better version strings (e.g.
simplepush-1.0.0 or ups-1.2.4). And this works great
So, I think it does make sense to stop hammering new issues into all the
different "technology silos", like AGDROID or AGPUSH. Instead I really
think we should unify one JIRA instance, with proper components and much
better version strings, allowing us to really use one instance for all of
AeroGear.
Today, to me, it does look a bit that our multiple instances of JIRA can be
really done w/ one JIRA (and components/versions) instead - we don't really
have much more value w/ all the different instances.
I'd like to retire the new instances, in the near future, moving forward
with just one JIRA instance. At some point - later this year - we could
than try to delete the other redundant JIRA silos.
Before retiring the instances, we will review the existing backlogs and
port over valid tickets. So no *relevant* ticket will be lost, and outdated
tickets kinda gets cleaned up, doing this excercise :-)
Feedback, thoughts, tomatos ?
-Matthias
--
Matthias Wessendorf
github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
6 years, 1 month