From jgallaso at redhat.com Thu Apr 6 06:56:01 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Thu, 6 Apr 2017 12:56:01 +0200 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource Message-ID: Hi all, I am trying to deploy UPS in Wildfly. In the step *Configure JMS destinations for the UnifiedPush* of the server installation instructions [1], I am getting this weird error: $ wildfly/bin/jboss-cli.sh > --file="~/projects/aerogear-unifiedpush-server/configuration/jms-setup-wildfly.cli" > The batch failed with the following error (you are remaining in the batch > editing mode to have a chance to correct the error): {"WFLYCTL0062: > Composite operation failed and was rolled back. Steps that failed:" => > {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ > (\"subsystem\" => \"messaging-activemq\"), > (\"server\" => \"default\"), > (\"jms-queue\" => \"AdmPushMessageQueue\") > ]"}} Any clue what this is about? ?[1] - https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation ? Cheers, -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile ? ? Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170406/14498241/attachment.html From supittma at redhat.com Thu Apr 6 08:31:46 2017 From: supittma at redhat.com (Summers Pittman) Date: Thu, 6 Apr 2017 08:31:46 -0400 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource In-Reply-To: References: Message-ID: It sounds like that resource already exists. To check use jboss-cli (in the /bin directory of wildfly) and run "ls subsystem=messaging-activemq/server=default/jms-queue". This will show you all of your created queues and if you see the ones from the jms-setup-wildfly script then you are already done. On Thu, Apr 6, 2017 at 6:56 AM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Hi all, > > I am trying to deploy UPS in Wildfly. In the step *Configure JMS > destinations for the UnifiedPush* of the server installation instructions > [1], I am getting this weird error: > > $ wildfly/bin/jboss-cli.sh --file="~/projects/aerogear-unifiedpush-server/ >> configuration/jms-setup-wildfly.cli" >> The batch failed with the following error (you are remaining in the batch >> editing mode to have a chance to correct the error): {"WFLYCTL0062: >> Composite operation failed and was rolled back. Steps that failed:" => >> {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ >> (\"subsystem\" => \"messaging-activemq\"), >> (\"server\" => \"default\"), >> (\"jms-queue\" => \"AdmPushMessageQueue\") >> ]"}} > > > Any clue what this is about? > > ?[1] - https://aerogear.org/docs/unifiedpush/ups_userguide/ > index/#server-installation? > > Cheers, > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > ? ? > > Red Hat > > > > M: +34618488633 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170406/f6f455be/attachment-0001.html From jgallaso at redhat.com Thu Apr 6 10:01:00 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Thu, 6 Apr 2017 16:01:00 +0200 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource In-Reply-To: References: Message-ID: OK, that's not the problem then. This is what I got when I try to deploy ag-push and auth-server: ag-push.war > 15:58:41,280 ERROR [org.jboss.as.controller.management-operation] > (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - > address: ([("deployment" => "ag-push.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => > ["jboss.naming.context.java.jboss.datasources.UnifiedPushDS"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\" is > missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]", > > "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\".__FIRST_PHASE__ > is missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]" > ] > } auth-server.war > 15:58:33,191 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool > -- 98) 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.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:209) > at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) > at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:42) > at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:30) > at > org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:103) > 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:103) > at > org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:59) > at > org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:161) > at > org.keycloak.services.managers.ApplianceBootstrap.setupDefaultRealm(ApplianceBootstrap.java:32) > at > org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:81) > 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:423) > 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:202) > ... 46 more > 15:58:33,196 ERROR [org.jboss.as.controller.management-operation] > (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - > address: ([("deployment" => "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 > } On 6 April 2017 at 14:31, Summers Pittman wrote: > It sounds like that resource already exists. > > To check use jboss-cli (in the /bin directory of wildfly) and run "ls > subsystem=messaging-activemq/server=default/jms-queue". This will show > you all of your created queues and if you see the ones from the > jms-setup-wildfly script then you are already done. > > On Thu, Apr 6, 2017 at 6:56 AM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Hi all, >> >> I am trying to deploy UPS in Wildfly. In the step *Configure JMS >> destinations for the UnifiedPush* of the server installation >> instructions [1], I am getting this weird error: >> >> $ wildfly/bin/jboss-cli.sh --file="~/projects/aerogear-un >>> ifiedpush-server/configuration/jms-setup-wildfly.cli" >>> The batch failed with the following error (you are remaining in the >>> batch editing mode to have a chance to correct the error): {"WFLYCTL0062: >>> Composite operation failed and was rolled back. Steps that failed:" => >>> {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ >>> (\"subsystem\" => \"messaging-activemq\"), >>> (\"server\" => \"default\"), >>> (\"jms-queue\" => \"AdmPushMessageQueue\") >>> ]"}} >> >> >> Any clue what this is about? >> >> ?[1] - https://aerogear.org/docs/unifiedpush/ups_userguide/index/# >> server-installation? >> >> Cheers, >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> ? ? >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170406/ed7cae1f/attachment-0001.html From jgallaso at redhat.com Thu Apr 6 10:07:39 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Thu, 6 Apr 2017 16:07:39 +0200 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource In-Reply-To: References: Message-ID: This is the whole Wildfly log: https://gist.github.com/josemigallas/ec120fe9c1a4a14f7d14c956cef030ba On 6 April 2017 at 16:01, Jose Miguel Gallas Olmedo wrote: > OK, that's not the problem then. This is what I got when I try to deploy > ag-push and auth-server: > > ag-push.war > >> 15:58:41,280 ERROR [org.jboss.as.controller.management-operation] >> (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - >> address: ([("deployment" => "ag-push.war")]) - failure description: { >> "WFLYCTL0412: Required services that are not installed:" => >> ["jboss.naming.context.java.jboss.datasources.UnifiedPushDS"], >> "WFLYCTL0180: Services with missing/unavailable dependencies" => [ >> "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\" is >> missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]", >> "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\".__FIRST_PHASE__ >> is missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]" >> ] >> } > > > auth-server.war > >> 15:58:33,191 ERROR [org.jboss.msc.service.fail] (ServerService Thread >> Pool -- 98) 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.ServletRequestContextThreadSet >> upAction$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:209) >> at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa >> ctory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) >> at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa >> ctory.create(DefaultJpaConnectionProviderFactory.java:42) >> at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa >> ctory.create(DefaultJpaConnectionProviderFactory.java:30) >> at org.keycloak.services.DefaultKeycloakSession.getProvider( >> DefaultKeycloakSession.java:103) >> 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:103) >> at org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider. >> getDelegate(DefaultCacheRealmProvider.java:59) >> at org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider. >> getRealm(DefaultCacheRealmProvider.java:161) >> at org.keycloak.services.managers.ApplianceBootstrap.setupDefaultRealm( >> ApplianceBootstrap.java:32) >> at org.keycloak.services.resources.KeycloakApplication. >> (KeycloakApplication.java:81) >> 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:423) >> 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:202) >> ... 46 more >> 15:58:33,196 ERROR [org.jboss.as.controller.management-operation] >> (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - >> address: ([("deployment" => "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 >> } > > > > On 6 April 2017 at 14:31, Summers Pittman wrote: > >> It sounds like that resource already exists. >> >> To check use jboss-cli (in the /bin directory of wildfly) and run "ls >> subsystem=messaging-activemq/server=default/jms-queue". This will show >> you all of your created queues and if you see the ones from the >> jms-setup-wildfly script then you are already done. >> >> On Thu, Apr 6, 2017 at 6:56 AM, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >>> Hi all, >>> >>> I am trying to deploy UPS in Wildfly. In the step *Configure JMS >>> destinations for the UnifiedPush* of the server installation >>> instructions [1], I am getting this weird error: >>> >>> $ wildfly/bin/jboss-cli.sh --file="~/projects/aerogear-un >>>> ifiedpush-server/configuration/jms-setup-wildfly.cli" >>>> The batch failed with the following error (you are remaining in the >>>> batch editing mode to have a chance to correct the error): {"WFLYCTL0062: >>>> Composite operation failed and was rolled back. Steps that failed:" => >>>> {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ >>>> (\"subsystem\" => \"messaging-activemq\"), >>>> (\"server\" => \"default\"), >>>> (\"jms-queue\" => \"AdmPushMessageQueue\") >>>> ]"}} >>> >>> >>> Any clue what this is about? >>> >>> ?[1] - https://aerogear.org/docs/unifiedpush/ups_userguide/index/#s >>> erver-installation? >>> >>> Cheers, >>> >>> -- >>> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> ? ? >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170406/1cb1c712/attachment-0001.html From matzew at apache.org Thu Apr 6 16:35:16 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 06 Apr 2017 20:35:16 +0000 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource In-Reply-To: References: Message-ID: Did you configure the DB? And is that one running? On Thu, 6 Apr 2017 at 17:06, Jose Miguel Gallas Olmedo wrote: > This is the whole Wildfly log: > https://gist.github.com/josemigallas/ec120fe9c1a4a14f7d14c956cef030ba > > On 6 April 2017 at 16:01, Jose Miguel Gallas Olmedo > wrote: > > OK, that's not the problem then. This is what I got when I try to deploy > ag-push and auth-server: > > ag-push.war > > 15:58:41,280 ERROR [org.jboss.as.controller.management-operation] > (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - > address: ([("deployment" => "ag-push.war")]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => > ["jboss.naming.context.java.jboss.datasources.UnifiedPushDS"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => [ > "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\" is > missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]", > > "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\".__FIRST_PHASE__ > is missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]" > ] > } > > > auth-server.war > > 15:58:33,191 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool > -- 98) 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.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:209) > at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) > at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:42) > at > org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:30) > at > org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:103) > 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:103) > at > org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:59) > at > org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:161) > at > org.keycloak.services.managers.ApplianceBootstrap.setupDefaultRealm(ApplianceBootstrap.java:32) > at > org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:81) > 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:423) > 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:202) > ... 46 more > 15:58:33,196 ERROR [org.jboss.as.controller.management-operation] > (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - > address: ([("deployment" => "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 > } > > > > On 6 April 2017 at 14:31, Summers Pittman wrote: > > It sounds like that resource already exists. > > To check use jboss-cli (in the /bin directory of wildfly) and run "ls > subsystem=messaging-activemq/server=default/jms-queue". This will show you > all of your created queues and if you see the ones from the > jms-setup-wildfly script then you are already done. > > On Thu, Apr 6, 2017 at 6:56 AM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > > Hi all, > > I am trying to deploy UPS in Wildfly. In the step *Configure JMS > destinations for the UnifiedPush* of the server installation instructions > [1], I am getting this weird error: > > $ wildfly/bin/jboss-cli.sh > --file="~/projects/aerogear-unifiedpush-server/configuration/jms-setup-wildfly.cli" > The batch failed with the following error (you are remaining in the batch > editing mode to have a chance to correct the error): {"WFLYCTL0062: > Composite operation failed and was rolled back. Steps that failed:" => > {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ > (\"subsystem\" => \"messaging-activemq\"), > (\"server\" => \"default\"), > (\"jms-queue\" => \"AdmPushMessageQueue\") > ]"}} > > > Any clue what this is about? > > ?[1] - > https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation > ? > > Cheers, > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > ? ? > > Red Hat > > > > M: +34618488633 > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > > > > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170406/59293d22/attachment-0001.html From matzew at apache.org Thu Apr 6 16:37:05 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 06 Apr 2017 20:37:05 +0000 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource References: Message-ID: Also, on WF 10.x we only support the master branch of UPS. On Thu, 6 Apr 2017 at 22:35, Matthias Wessendorf wrote: > Did you configure the DB? And is that one running? > > On Thu, 6 Apr 2017 at 17:06, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> This is the whole Wildfly log: >> https://gist.github.com/josemigallas/ec120fe9c1a4a14f7d14c956cef030ba >> >> On 6 April 2017 at 16:01, Jose Miguel Gallas Olmedo >> wrote: >> >> OK, that's not the problem then. This is what I got when I try to deploy >> ag-push and auth-server: >> >> ag-push.war >> >> 15:58:41,280 ERROR [org.jboss.as.controller.management-operation] >> (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - >> address: ([("deployment" => "ag-push.war")]) - failure description: { >> "WFLYCTL0412: Required services that are not installed:" => >> ["jboss.naming.context.java.jboss.datasources.UnifiedPushDS"], >> "WFLYCTL0180: Services with missing/unavailable dependencies" => [ >> "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\" is >> missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]", >> >> "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\".__FIRST_PHASE__ >> is missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]" >> ] >> } >> >> >> auth-server.war >> >> 15:58:33,191 ERROR [org.jboss.msc.service.fail] (ServerService Thread >> Pool -- 98) 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.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:209) >> at >> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) >> at >> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:42) >> at >> org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:30) >> at >> org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:103) >> 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:103) >> at >> org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:59) >> at >> org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:161) >> at >> org.keycloak.services.managers.ApplianceBootstrap.setupDefaultRealm(ApplianceBootstrap.java:32) >> at >> org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:81) >> 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:423) >> 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:202) >> ... 46 more >> 15:58:33,196 ERROR [org.jboss.as.controller.management-operation] >> (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - >> address: ([("deployment" => "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 >> } >> >> >> >> On 6 April 2017 at 14:31, Summers Pittman wrote: >> >> It sounds like that resource already exists. >> >> To check use jboss-cli (in the /bin directory of wildfly) and run "ls >> subsystem=messaging-activemq/server=default/jms-queue". This will show you >> all of your created queues and if you see the ones from the >> jms-setup-wildfly script then you are already done. >> >> On Thu, Apr 6, 2017 at 6:56 AM, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >> Hi all, >> >> I am trying to deploy UPS in Wildfly. In the step *Configure JMS >> destinations for the UnifiedPush* of the server installation >> instructions [1], I am getting this weird error: >> >> $ wildfly/bin/jboss-cli.sh >> --file="~/projects/aerogear-unifiedpush-server/configuration/jms-setup-wildfly.cli" >> The batch failed with the following error (you are remaining in the batch >> editing mode to have a chance to correct the error): {"WFLYCTL0062: >> Composite operation failed and was rolled back. Steps that failed:" => >> {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ >> (\"subsystem\" => \"messaging-activemq\"), >> (\"server\" => \"default\"), >> (\"jms-queue\" => \"AdmPushMessageQueue\") >> ]"}} >> >> >> Any clue what this is about? >> >> ?[1] - >> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation >> ? >> >> Cheers, >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> ? ? >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> >> >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- > Sent from Gmail Mobile > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170406/da9bcdde/attachment-0001.html From jgallaso at redhat.com Fri Apr 7 03:14:24 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 7 Apr 2017 09:14:24 +0200 Subject: [aerogear-dev] Error WFLYCTL0212: Duplicate resource In-Reply-To: References: Message-ID: I think that was the problem, the DB, I did not deploy it I think. Thanks Matthias! On 6 April 2017 at 22:37, Matthias Wessendorf wrote: > Also, > > on WF 10.x we only support the master branch of UPS. > > > > On Thu, 6 Apr 2017 at 22:35, Matthias Wessendorf > wrote: > >> Did you configure the DB? And is that one running? >> >> On Thu, 6 Apr 2017 at 17:06, Jose Miguel Gallas Olmedo < >> jgallaso at redhat.com> wrote: >> >>> This is the whole Wildfly log: https://gist.github.com/josemigallas/ >>> ec120fe9c1a4a14f7d14c956cef030ba >>> >>> On 6 April 2017 at 16:01, Jose Miguel Gallas Olmedo >> > wrote: >>> >>> OK, that's not the problem then. This is what I got when I try to deploy >>> ag-push and auth-server: >>> >>> ag-push.war >>> >>> 15:58:41,280 ERROR [org.jboss.as.controller.management-operation] >>> (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - >>> address: ([("deployment" => "ag-push.war")]) - failure description: { >>> "WFLYCTL0412: Required services that are not installed:" => >>> ["jboss.naming.context.java.jboss.datasources.UnifiedPushDS"], >>> "WFLYCTL0180: Services with missing/unavailable dependencies" => [ >>> "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\" is >>> missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]", >>> "jboss.persistenceunit.\"ag-push.war#unifiedpush-default\".__FIRST_PHASE__ >>> is missing [jboss.naming.context.java.jboss.datasources.UnifiedPushDS]" >>> ] >>> } >>> >>> >>> auth-server.war >>> >>> 15:58:33,191 ERROR [org.jboss.msc.service.fail] (ServerService Thread >>> Pool -- 98) 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.ServletRequestContextThreadSet >>> upAction$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:209) >>> at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa >>> ctory.lazyInit(DefaultJpaConnectionProviderFactory.java:130) >>> at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa >>> ctory.create(DefaultJpaConnectionProviderFactory.java:42) >>> at org.keycloak.connections.jpa.DefaultJpaConnectionProviderFa >>> ctory.create(DefaultJpaConnectionProviderFactory.java:30) >>> at org.keycloak.services.DefaultKeycloakSession.getProvider( >>> DefaultKeycloakSession.java:103) >>> 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:103) >>> at org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider. >>> getDelegate(DefaultCacheRealmProvider.java:59) >>> at org.keycloak.models.cache.infinispan.DefaultCacheRealmProvider. >>> getRealm(DefaultCacheRealmProvider.java:161) >>> at org.keycloak.services.managers.ApplianceBootstrap.setupDefaultRealm( >>> ApplianceBootstrap.java:32) >>> at org.keycloak.services.resources.KeycloakApplication. >>> (KeycloakApplication.java:81) >>> 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:423) >>> 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:202) >>> ... 46 more >>> 15:58:33,196 ERROR [org.jboss.as.controller.management-operation] >>> (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - >>> address: ([("deployment" => "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 >>> } >>> >>> >>> >>> On 6 April 2017 at 14:31, Summers Pittman wrote: >>> >>> It sounds like that resource already exists. >>> >>> To check use jboss-cli (in the /bin directory of wildfly) and run "ls >>> subsystem=messaging-activemq/server=default/jms-queue". This will show >>> you all of your created queues and if you see the ones from the >>> jms-setup-wildfly script then you are already done. >>> >>> On Thu, Apr 6, 2017 at 6:56 AM, Jose Miguel Gallas Olmedo < >>> jgallaso at redhat.com> wrote: >>> >>> Hi all, >>> >>> I am trying to deploy UPS in Wildfly. In the step *Configure JMS >>> destinations for the UnifiedPush* of the server installation >>> instructions [1], I am getting this weird error: >>> >>> $ wildfly/bin/jboss-cli.sh --file="~/projects/aerogear- >>> unifiedpush-server/configuration/jms-setup-wildfly.cli" >>> The batch failed with the following error (you are remaining in the >>> batch editing mode to have a chance to correct the error): {"WFLYCTL0062: >>> Composite operation failed and was rolled back. Steps that failed:" => >>> {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ >>> (\"subsystem\" => \"messaging-activemq\"), >>> (\"server\" => \"default\"), >>> (\"jms-queue\" => \"AdmPushMessageQueue\") >>> ]"}} >>> >>> >>> Any clue what this is about? >>> >>> ?[1] - https://aerogear.org/docs/unifiedpush/ups_userguide/ >>> index/#server-installation? >>> >>> Cheers, >>> >>> -- >>> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> ? ? >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >>> >>> >>> >>> -- >>> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> >>> >>> >>> >>> -- >>> >>> JOSE MIGUEL GALLAS OLMEDO >>> >>> ASSOCIATE QE, mobile >>> >>> Red Hat >>> >>> >>> >>> M: +34618488633 >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> -- >> Sent from Gmail Mobile >> > -- > Sent from Gmail Mobile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170407/8d01662c/attachment-0001.html From dimitrazuccarelli at gmail.com Mon Apr 10 05:23:53 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Mon, 10 Apr 2017 10:23:53 +0100 Subject: [aerogear-dev] UPS Openshift Template Message-ID: Hi, I'm looking into getting started on an Openshift template for UPS. Is anyone already looking at this? Do you have any pointers? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170410/5082591b/attachment.html From matzew at apache.org Mon Apr 10 05:45:22 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Mon, 10 Apr 2017 11:45:22 +0200 Subject: [aerogear-dev] UPS Openshift Template In-Reply-To: References: Message-ID: Hi Dimitra, we do only have docker images, for the UPS: https://github.com/aerogear/dockerfiles/tree/master/wildfly/unifiedpush-wildfly We do have a compose (v1) file, that links the Server (based on WildFly 10.x) to the DB images (one for Keycloak, one for Push): https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/docker-compose I think that Summers was looking at Openshift template for UPS, and he got something running, or close to it. I think one issue w/ our current issues is, that some of the V1 docker/compose links and their EVNs are not really working on Openshift. Perhaps migrating the compose file to v2 (or 3) is a good starting point? Just a thought, not really sure, tbh -M On Mon, Apr 10, 2017 at 11:23 AM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Hi, > > I'm looking into getting started on an Openshift template for UPS. Is > anyone already looking at this? Do you have any pointers? > > Thanks! > > _______________________________________________ > 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-dev/attachments/20170410/d6574806/attachment.html From wtrocki at redhat.com Mon Apr 10 05:45:06 2017 From: wtrocki at redhat.com (Wojciech Trocki) Date: Mon, 10 Apr 2017 10:45:06 +0100 Subject: [aerogear-dev] UPS Openshift Template In-Reply-To: References: Message-ID: We have community docker images. It's easy to have template from there. We got that sorted :) WOJCIECH TROCKI SOFTWARE ENGINEER Red Hat Mobile IM: wtrocki On Mon, Apr 10, 2017 at 10:23 AM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Hi, > > I'm looking into getting started on an Openshift template for UPS. Is > anyone already looking at this? Do you have any pointers? > > Thanks! > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170410/f4f6b4d1/attachment.html From dimitrazuccarelli at gmail.com Mon Apr 10 07:31:28 2017 From: dimitrazuccarelli at gmail.com (Dimitra Zuccarelli) Date: Mon, 10 Apr 2017 12:31:28 +0100 Subject: [aerogear-dev] UPS Openshift Template In-Reply-To: References: Message-ID: Ok, great. As a first step I'll get started on migrating the docker-compose file from v1 to a later version then. On Mon, Apr 10, 2017 at 10:45 AM, Matthias Wessendorf wrote: > Hi Dimitra, > > we do only have docker images, for the UPS: > https://github.com/aerogear/dockerfiles/tree/master/ > wildfly/unifiedpush-wildfly > > We do have a compose (v1) file, that links the Server (based on WildFly > 10.x) to the DB images (one for Keycloak, one for Push): > https://github.com/aerogear/aerogear-unifiedpush-server/ > tree/master/docker-compose > > I think that Summers was looking at Openshift template for UPS, and he got > something running, or close to it. > > I think one issue w/ our current issues is, that some of the V1 > docker/compose links and their EVNs are not really working on Openshift. > Perhaps migrating the compose file to v2 (or 3) is a good starting point? > Just a thought, not really sure, tbh > > -M > > > On Mon, Apr 10, 2017 at 11:23 AM, Dimitra Zuccarelli < > dimitrazuccarelli at gmail.com> wrote: > >> Hi, >> >> I'm looking into getting started on an Openshift template for UPS. Is >> anyone already looking at this? Do you have any pointers? >> >> Thanks! >> >> _______________________________________________ >> 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-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170410/1e2a4e65/attachment.html From supittma at redhat.com Mon Apr 10 07:44:30 2017 From: supittma at redhat.com (Summers Pittman) Date: Mon, 10 Apr 2017 07:44:30 -0400 Subject: [aerogear-dev] UPS Openshift Template In-Reply-To: References: Message-ID: Oh hey I'm actually working on one based on a blog post I made last week. https://blog.sagaoftherealms.net/?p=644 On Mon, Apr 10, 2017 at 7:31 AM, Dimitra Zuccarelli < dimitrazuccarelli at gmail.com> wrote: > Ok, great. > As a first step I'll get started on migrating the docker-compose file from > v1 to a later version then. > > On Mon, Apr 10, 2017 at 10:45 AM, Matthias Wessendorf > wrote: > >> Hi Dimitra, >> >> we do only have docker images, for the UPS: >> https://github.com/aerogear/dockerfiles/tree/master/wildfly/ >> unifiedpush-wildfly >> >> We do have a compose (v1) file, that links the Server (based on WildFly >> 10.x) to the DB images (one for Keycloak, one for Push): >> https://github.com/aerogear/aerogear-unifiedpush-server/tree >> /master/docker-compose >> >> I think that Summers was looking at Openshift template for UPS, and he >> got something running, or close to it. >> >> I think one issue w/ our current issues is, that some of the V1 >> docker/compose links and their EVNs are not really working on Openshift. >> Perhaps migrating the compose file to v2 (or 3) is a good starting point? >> Just a thought, not really sure, tbh >> >> -M >> >> >> On Mon, Apr 10, 2017 at 11:23 AM, Dimitra Zuccarelli < >> dimitrazuccarelli at gmail.com> wrote: >> >>> Hi, >>> >>> I'm looking into getting started on an Openshift template for UPS. Is >>> anyone already looking at this? Do you have any pointers? >>> >>> Thanks! >>> >>> _______________________________________________ >>> 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-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170410/ba508a07/attachment-0001.html From supittma at redhat.com Mon Apr 10 10:58:03 2017 From: supittma at redhat.com (Summers Pittman) Date: Mon, 10 Apr 2017 10:58:03 -0400 Subject: [aerogear-dev] UPS Openshift Template In-Reply-To: References: Message-ID: OK, I finished my UPS template : https://github.com/secondsun/ups-docker-openshift-template/blob/master/ups-template.json It works on my machine, but if you guys don't mind whacking it some and giving me feedback then I can make a proper PR to the AeroGear project. Summers On Mon, Apr 10, 2017 at 7:44 AM, Summers Pittman wrote: > Oh hey I'm actually working on one based on a blog post I made last week. > > https://blog.sagaoftherealms.net/?p=644 > > > > On Mon, Apr 10, 2017 at 7:31 AM, Dimitra Zuccarelli < > dimitrazuccarelli at gmail.com> wrote: > >> Ok, great. >> As a first step I'll get started on migrating the docker-compose file >> from v1 to a later version then. >> >> On Mon, Apr 10, 2017 at 10:45 AM, Matthias Wessendorf >> wrote: >> >>> Hi Dimitra, >>> >>> we do only have docker images, for the UPS: >>> https://github.com/aerogear/dockerfiles/tree/master/wildfly/ >>> unifiedpush-wildfly >>> >>> We do have a compose (v1) file, that links the Server (based on WildFly >>> 10.x) to the DB images (one for Keycloak, one for Push): >>> https://github.com/aerogear/aerogear-unifiedpush-server/tree >>> /master/docker-compose >>> >>> I think that Summers was looking at Openshift template for UPS, and he >>> got something running, or close to it. >>> >>> I think one issue w/ our current issues is, that some of the V1 >>> docker/compose links and their EVNs are not really working on Openshift. >>> Perhaps migrating the compose file to v2 (or 3) is a good starting point? >>> Just a thought, not really sure, tbh >>> >>> -M >>> >>> >>> On Mon, Apr 10, 2017 at 11:23 AM, Dimitra Zuccarelli < >>> dimitrazuccarelli at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I'm looking into getting started on an Openshift template for UPS. Is >>>> anyone already looking at this? Do you have any pointers? >>>> >>>> Thanks! >>>> >>>> _______________________________________________ >>>> 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-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170410/4c18ba3e/attachment.html From supittma at redhat.com Tue Apr 11 16:30:07 2017 From: supittma at redhat.com (Summers Pittman) Date: Tue, 11 Apr 2017 16:30:07 -0400 Subject: [aerogear-dev] UnifiedPush OpenShift Template PR Message-ID: Hey guys, I've put together a ups template for open shift. It uses the Docker image aerogear/unifiedpush-wildfly. I would love your feedback here : https://github.com/aerogear/aerogear-unifiedpush-server/pull/817 I can also update the README with instructions. Summers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170411/04d61f9e/attachment.html From jgallaso at redhat.com Thu Apr 20 07:31:42 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Thu, 20 Apr 2017 13:31:42 +0200 Subject: [aerogear-dev] Question about metricsEndpoint Message-ID: Hi all, I am trying to solve some bugish behaviour that makes the status label to be "Pending..." permanently, even when the notifications have been sent. The label is "Pending..." when "*servedVariants*" is less than " *totalVariants*" -> https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.x-dev/admin-ui/app/components/app-detail/include/activity.html#L46 Well, in the *metricsEndpoint.js*, it iterates over all variants and flag an error or increase the "*servedVariants*" property -> https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.x-dev/admin-ui/app/scripts/endpoints/metricsEndpoint.js#L28-L30 ?I don't fully understand what's happening in this iteration and why there's no "else" clause. The problem is caused by this I think. During some iteration the counter is not being increased hence the *servedVariants* never equals *totalVariants* and hence (again) the label does not change.? So the current flow would be: 1. If *deliveryStatus* is falsy, flag an error. 2. If servedBatches = totalBatches then increase servedVariants Can both conditions pass? I think they can although this is not expected. Can deliveryStatus be always truthy but the servedBatches != totalBatches? I think that what's happening and as a result, it is hiding some error that the user may want to see. I also think that, in case of deliveryStatus, the iteration should stop. WDYT? ?Cheers,? -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170420/5727b57f/attachment.html From matzew at apache.org Thu Apr 20 08:29:55 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Apr 2017 14:29:55 +0200 Subject: [aerogear-dev] Question about metricsEndpoint In-Reply-To: References: Message-ID: Mind sending a PR ? On Thu, Apr 20, 2017 at 1:31 PM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Hi all, > > I am trying to solve some bugish behaviour that makes the status label to > be "Pending..." permanently, even when the notifications have been sent. > > The label is "Pending..." when "*servedVariants*" is less than " > *totalVariants*" -> https://github.com/aerogear/aerogear-unifiedpush- > server/blob/1.1.x-dev/admin-ui/app/components/app-detail/ > include/activity.html#L46 > > Well, in the *metricsEndpoint.js*, it iterates over all variants and flag > an error or increase the "*servedVariants*" property -> > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/1.1.x-dev/admin-ui/app/scripts/endpoints/metricsEndpoint.js#L28-L30 > > ?I don't fully understand what's happening in this iteration and why > there's no "else" clause. The problem is caused by this I think. During > some iteration the counter is not being increased hence the > *servedVariants* never equals *totalVariants* and hence (again) the label > does not change.? > > So the current flow would be: > 1. If *deliveryStatus* is falsy, flag an error. > 2. If servedBatches = totalBatches then increase servedVariants > > Can both conditions pass? I think they can although this is not expected. > Can deliveryStatus be always truthy but the servedBatches != totalBatches? > I think that what's happening and as a result, it is hiding some error that > the user may want to see. > > I also think that, in case of deliveryStatus, the iteration should stop. > > WDYT? > > ?Cheers,? > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > > _______________________________________________ > 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-dev/attachments/20170420/44f652d9/attachment-0001.html From jgallaso at redhat.com Thu Apr 20 09:41:43 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Thu, 20 Apr 2017 15:41:43 +0200 Subject: [aerogear-dev] Question about metricsEndpoint In-Reply-To: References: Message-ID: ?But I am asking for a clarification of this code, I cannot send a fix if I don't understand what this does.? On 20 April 2017 at 14:29, Matthias Wessendorf wrote: > Mind sending a PR ? > > On Thu, Apr 20, 2017 at 1:31 PM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Hi all, >> >> I am trying to solve some bugish behaviour that makes the status label to >> be "Pending..." permanently, even when the notifications have been sent. >> >> The label is "Pending..." when "*servedVariants*" is less than " >> *totalVariants*" -> https://github.com/aerogear >> /aerogear-unifiedpush-server/blob/1.1.x-dev/admin-ui/app/ >> components/app-detail/include/activity.html#L46 >> >> Well, in the *metricsEndpoint.js*, it iterates over all variants and >> flag an error or increase the "*servedVariants*" property -> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob >> /1.1.x-dev/admin-ui/app/scripts/endpoints/metricsEndpoint.js#L28-L30 >> >> ?I don't fully understand what's happening in this iteration and why >> there's no "else" clause. The problem is caused by this I think. During >> some iteration the counter is not being increased hence the >> *servedVariants* never equals *totalVariants* and hence (again) the >> label does not change.? >> >> So the current flow would be: >> 1. If *deliveryStatus* is falsy, flag an error. >> 2. If servedBatches = totalBatches then increase servedVariants >> >> Can both conditions pass? I think they can although this is not expected. >> Can deliveryStatus be always truthy but the servedBatches != >> totalBatches? I think that what's happening and as a result, it is hiding >> some error that the user may want to see. >> >> I also think that, in case of deliveryStatus, the iteration should stop. >> >> WDYT? >> >> ?Cheers,? >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> _______________________________________________ >> 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-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170420/e7416730/attachment.html From matzew at apache.org Thu Apr 20 11:56:37 2017 From: matzew at apache.org (Matthias Wessendorf) Date: Thu, 20 Apr 2017 17:56:37 +0200 Subject: [aerogear-dev] Question about metricsEndpoint In-Reply-To: References: Message-ID: On Thu, Apr 20, 2017 at 1:31 PM, Jose Miguel Gallas Olmedo < jgallaso at redhat.com> wrote: > Hi all, > > I am trying to solve some bugish behaviour that makes the status label to > be "Pending..." permanently, even when the notifications have been sent. > > The label is "Pending..." when "*servedVariants*" is less than " > *totalVariants*" -> https://github.com/aerogear > /aerogear-unifiedpush-server/blob/1.1.x-dev/admin-ui/app/ > components/app-detail/include/activity.html#L46 > > Well, in the *metricsEndpoint.js*, it iterates over all variants and flag > an error or increase the "*servedVariants*" property -> > https://github.com/aerogear/aerogear-unifiedpush-server/blob > /1.1.x-dev/admin-ui/app/scripts/endpoints/metricsEndpoint.js#L28-L30 > > ?I don't fully understand what's happening in this iteration and why > there's no "else" clause. The problem is caused by this I think. During > some iteration the counter is not being increased hence the > *servedVariants* never equals *totalVariants* and hence (again) the label > does not change.? > > So the current flow would be: > 1. If *deliveryStatus* is falsy, flag an error. > 2. If servedBatches = totalBatches then increase servedVariants > > Can both conditions pass? I think they can although this is not expected. > with two conditions? > Can deliveryStatus be always truthy but the servedBatches != totalBatches? > Yes, each batch uses a Sender, which signals if it could submit something to the provider: https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.1.x-dev/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/NotificationDispatcher.java#L94-L98 now, when we have 10 batches, starting in batch one we do set the status to true, and we continue to do so (if success) on all other coming batches. On the server I noticed a timing issue, with the internal processing of the metrics payload via JMS > I think that what's happening and as a result, it is hiding some error > that the user may want to see. > > I also think that, in case of deliveryStatus, the iteration should stop. > > WDYT? > > ?Cheers,? > > -- > > JOSE MIGUEL GALLAS OLMEDO > > ASSOCIATE QE, mobile > > Red Hat > > > > M: +34618488633 > > > > _______________________________________________ > 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-dev/attachments/20170420/2015dd08/attachment.html From jgallaso at redhat.com Fri Apr 21 03:55:33 2017 From: jgallaso at redhat.com (Jose Miguel Gallas Olmedo) Date: Fri, 21 Apr 2017 09:55:33 +0200 Subject: [aerogear-dev] Question about metricsEndpoint In-Reply-To: References: Message-ID: > > Which 2 conditions? The 2 conditions in the loop: angular.forEach(metric.variantInformations, function (variantMetric) { metric.totalReceivers += variantMetric.receivers; if ( *??!variantMetric.deliveryStatus*) { metric.deliveryFailed = true; } if ( *??variantMetric.servedBatches === variantMetric.totalBatches*) { metric.servedVariants += 1; } }); If there's a failure and deliveryFailed is set to true, there should be no need of increasing servedVariants counter, I think this is not robust code. Yes, each batch uses a Sender, which signals if it could submit something > to the provider: > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/1.1.x-dev/push/sender/src/main/java/org/jboss/ > aerogear/unifiedpush/message/NotificationDispatcher.java#L94-L98 Then we should keep track of "unservedVariants" so we know when all variants have been processed (not served). Because if 1 variant has not been served and deliveryStatus is falsy, the label in the Activity Log will be permanently "Pending". I'm not really suggesting anything in particular, just trying to understand this code. So please correct me if I'm wrong. On 20 April 2017 at 17:56, Matthias Wessendorf wrote: > > > On Thu, Apr 20, 2017 at 1:31 PM, Jose Miguel Gallas Olmedo < > jgallaso at redhat.com> wrote: > >> Hi all, >> >> I am trying to solve some bugish behaviour that makes the status label to >> be "Pending..." permanently, even when the notifications have been sent. >> >> The label is "Pending..." when "*servedVariants*" is less than " >> *totalVariants*" -> https://github.com/aerogear >> /aerogear-unifiedpush-server/blob/1.1.x-dev/admin-ui/app/com >> ponents/app-detail/include/activity.html#L46 >> >> Well, in the *metricsEndpoint.js*, it iterates over all variants and >> flag an error or increase the "*servedVariants*" property -> >> https://github.com/aerogear/aerogear-unifiedpush-server/blob >> /1.1.x-dev/admin-ui/app/scripts/endpoints/metricsEndpoint.js#L28-L30 >> >> ?I don't fully understand what's happening in this iteration and why >> there's no "else" clause. The problem is caused by this I think. During >> some iteration the counter is not being increased hence the >> *servedVariants* never equals *totalVariants* and hence (again) the >> label does not change.? >> >> So the current flow would be: >> 1. If *deliveryStatus* is falsy, flag an error. >> 2. If servedBatches = totalBatches then increase servedVariants >> >> Can both conditions pass? I think they can although this is not expected. >> > > with two conditions? > > >> Can deliveryStatus be always truthy but the servedBatches != >> totalBatches? >> > > Yes, each batch uses a Sender, which signals if it could submit something > to the provider: > https://github.com/aerogear/aerogear-unifiedpush-server/ > blob/1.1.x-dev/push/sender/src/main/java/org/jboss/ > aerogear/unifiedpush/message/NotificationDispatcher.java#L94-L98 > > now, when we have 10 batches, starting in batch one we do set the status > to true, and we continue to do so (if success) on all other coming batches. > > > On the server I noticed a timing issue, with the internal processing of > the metrics payload via JMS > > > > >> I think that what's happening and as a result, it is hiding some error >> that the user may want to see. >> >> I also think that, in case of deliveryStatus, the iteration should stop. >> >> WDYT? >> >> ?Cheers,? >> >> -- >> >> JOSE MIGUEL GALLAS OLMEDO >> >> ASSOCIATE QE, mobile >> >> Red Hat >> >> >> >> M: +34618488633 >> >> >> >> _______________________________________________ >> 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-dev mailing list > aerogear-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- JOSE MIGUEL GALLAS OLMEDO ASSOCIATE QE, mobile Red Hat M: +34618488633 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20170421/0bca0cf9/attachment-0001.html