Swift 3 is on its way for AeroGear libraries
by Corinne Krych
Hello iOS lovers,
Swift3 is coming!
Today we released to CocoaPods aerogear-ios-http 1.0.0 for Swift3.
Thanks tuzonghua for reviewing and help.
aerogear-ios-push Swift3 is coming next.
aerogear-ios-oauth2 is progressing. @tuzonghua, PR welcome ;)
Community contribution on Swift3 migration is welcome!
++
Corinne
PS: I love new emoji from CocoaPods:
[image: Inline images 1]
8 years
Re: [Aerogear-users] Aerogear Websphere-liberty setup
by Gorla, Vinod (NonEmp)
Hi Aerogear team,
Currently UPS is supported for jboss. Is it possible to run it on WAS-liberty? If so can you suggest any prerequisites/config changes that I need to follow?
I am using 1.2.0-alpha-3 version of UPS. I understand that this version uses topics. So just configuring the topics and datasources(key cloak, unifiedpush) on WAS is sufficient?
Thanks
Vinod
From: <aerogear-users-bounces(a)lists.jboss.org<mailto:aerogear-users-bounces@lists.jboss.org>> on behalf of Matthias Wessendorf <matzew(a)apache.org<mailto:matzew@apache.org>>
Reply-To: "aerogear-users(a)lists.jboss.org<mailto:aerogear-users@lists.jboss.org>" <aerogear-users(a)lists.jboss.org<mailto:aerogear-users@lists.jboss.org>>
Date: Tuesday, November 1, 2016 at 4:24 AM
To: "aerogear-users(a)lists.jboss.org<mailto:aerogear-users@lists.jboss.org>" <aerogear-users(a)lists.jboss.org<mailto:aerogear-users@lists.jboss.org>>
Subject: Re: [Aerogear-users] Aerogear aerodoc set up
Otherwise, can you share your github branch / fork ?
On Tue, Nov 1, 2016 at 10:24 AM, Matthias Wessendorf <matzew(a)apache.org<mailto:matzew@apache.org>> wrote:
looks like it could not connect to the JBoss. Is it running ?
Make sure it builds again (mvn clean install) and than deploy ( mvn clean install jboss-as:deploy)
On Tue, Nov 1, 2016 at 10:10 AM, columfoskin <columfoskin(a)gmail.com<mailto:columfoskin@gmail.com>> wrote:
Hi Matthias,
I have been making a small change in the aerodoc application, nothing major
just some text or whatever to test being able to change something and
rebuild it again. The build passes but the "mvn clean install
jboss-as:deploy" fails every time. I reverted the change and it still will
not build properly. The build attempt results are attached, any help would
be greatly appreciated.
Thanks,
Colum.
<http://aerogear-users.1116366.n5.nabble.com/file/n933/Screenshot_2016-11-...<https://urldefense.proofpoint.com/v2/url?u=http-3A__aerogear-2Dusers.1116...>>
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Aerogear-aerod...<https://urldefense.proofpoint.com/v2/url?u=http-3A__aerogear-2Dusers.1116...>
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org<mailto:Aerogear-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.jboss.org_mail...>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/<https://urldefense.proofpoint.com/v2/url?u=http-3A__matthiaswessendorf.wo...>
twitter: http://twitter.com/mwessendorf<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_mwessendo...>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/<https://urldefense.proofpoint.com/v2/url?u=http-3A__matthiaswessendorf.wo...>
twitter: http://twitter.com/mwessendorf<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_mwessendo...>
________________________________
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
8 years
Unexpected error running Liquibase: Precondition Error
by Sonu Kumar Gupta
Dear Sir,
Pls. help
I am starting wildfly with ./standalone.sh --server-config=standalone-full.xml It works without errors.
I cloned latest aerogear-unifiedpush-server and installed with maven
I follow the steps in https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-install....
I am using postgres database. It is running on localhost and the port is 5432. postgres connector version is postgresql-9.4.1207.jar.
I created all databases. Generated the UnifiedPush Database and Datasource.
liquibase.properties contains the following info
url=jdbc:postgresql://localhost:5432/unifiedpush
driver=org.postgresql.Driver
username=unifiedpush
password=unifiedpush
changeLogFile=liquibase/master.xml
ON STEP 'CREATE THE DATABASE SCHEMA'
I run ./bin/ups-migrator update
I get the error 'Unexpected error running Liquibase: Precondition error'
Regards,
Sonu Kumar Gupta
8 years
Aerogear aerodoc set up
by colum foskin
Hi all,
I am in the process of trying to to get the aerodoc application up and running on my machine this week and I am having some issues with it - I am getting a build failure each time.
I have the push server running locally, using the docker image.
The readme for aerodoc just says run “mvn clean install jboss-as:deploy“ , however I think it is failing to build due to possibly having to configure aerodoc to point at my UPS, but I can’t find any info on this anywhere.
I would like to know if I am on the right track with it, as I had a look on the forums and could not see much about it. I have searched through the code base to see if this is configured somewhere but I am not having much luck with it.
Any help or info on how to get this running would be greatly appreciated.
Thanks,
Colum.
8 years
Re: [Aerogear-users] [aerogear-dev] Support for Aerogear
by Ali Ok
Hi Vinod,
Feedhenry (RHMAP) is fully supported by Red Hat. Aerogear components are
used in RHMAP, so they are active projects. For example, just recently we
released an initial version of Aerogear Digger [1].
Push is used as the main push technology in RHMAP, so you should expect a
good amount of activity and support in there.
You can check the repositories of push related things in Aerogear
organization [2]. You can see the activitiy there.
[1]: http://lists.jboss.org/pipermail/aerogear-dev/2016-October/012622.html
[2]: https://github.com/aerogear?utf8=%E2%9C%93&query=push
Cheers,
Ali
On Mon, Oct 31, 2016 at 11:53 PM, Gorla, Vinod (NonEmp) <
vinod.gorla(a)kroger.com> wrote:
> Hi Aerogear team,
>
> Now that Redhat has Feedhenry as mobile platform for both development and
> backend how much support will Aerogear receive from Redhat? I have read
> that LiveOak MBaaS is stopped. Can you please give me some info that would
> be helpful for me to make a right choice for the push platform?
>
>
> Thanks
> Vinod
>
> ------------------------------
>
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain information that is confidential and
> protected by law from unauthorized disclosure. Any unauthorized review,
> use, disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of the original message.
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
8 years
Re: [Aerogear-users] [aerogear-dev] Support for Aerogear
by Matthias Wessendorf
Hello,
the Unified Push Server is part of the Red Hat Mobile Application Platform
(RHMAP):
http://blog.feedhenry.com/release-of-rhmap-3-6-0-including-unified-push-s...
HTH,
Matthias
On Mon, Oct 31, 2016 at 9:53 PM, Gorla, Vinod (NonEmp) <
vinod.gorla(a)kroger.com> wrote:
> Hi Aerogear team,
>
> Now that Redhat has Feedhenry as mobile platform for both development and
> backend how much support will Aerogear receive from Redhat? I have read
> that LiveOak MBaaS is stopped. Can you please give me some info that would
> be helpful for me to make a right choice for the push platform?
>
>
> Thanks
> Vinod
>
> ------------------------------
>
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain information that is confidential and
> protected by law from unauthorized disclosure. Any unauthorized review,
> use, disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of the original message.
>
> _______________________________________________
> 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
8 years
Log file size
by Sonu Kumar Gupta
Dear Sir,
We have configured wildfly10 on Ubuntu 14.04. It was running well from last 3 days log file size is too large i.e. 300 GB or more and when we monitor the log file it continuously write and file size increased rapidly.
# du -sh /var/log/wildfly/console.log
248G /var/log/wildfly/console.log
# du -sh /srv/wildfly-10.0.0.Final/standalone/log/server.log
306G /srv/wildfly-10.0.0.Final/standalone/log/server.log
#tailf /srv/wildfly-10.0.0.Final/standalone/log/server.log
2016-11-01 00:00:00,300 ERROR [org.jboss.as.ejb3.invocation] (Thread-159 (ActiveMQ-client-global-threads-1710962884)) WFLYEJB0034: EJB Invocation failed on component PushMessageMetricsService for method public void org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService.lock(org.jboss.aerogear.unifiedpush.api.PushMessageInformation): javax.ejb.EJBTransactionRolledbackException: entity not in the persistence context
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:159)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
8 years
