[JBoss JIRA] (WFLY-11084) inter-app quickstart does not deploy (WildFly 14.0.1)
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11084?page=com.atlassian.jira.plugin... ]
Brian Stansberry edited comment on WFLY-11084 at 10/19/18 3:25 PM:
-------------------------------------------------------------------
I'm rejecting this as there's a duplicate of it (WFLY-11211) and that one seems to be more oriented (Component, Assignee, etc) toward dealing with the Quickstart as opposed to changing the server.
was (Author: brian.stansberry):
I'm rejecting this as there's a duplicate of it (WFLY-11211) and that one seems to be more oriented toward dealing with the Quickstart as opposed to changing the server.
> inter-app quickstart does not deploy (WildFly 14.0.1)
> -----------------------------------------------------
>
> Key: WFLY-11084
> URL: https://issues.jboss.org/browse/WFLY-11084
> Project: WildFly
> Issue Type: Bug
> Reporter: Kevin Eagles
> Assignee: Bartosz Baranowski
> Priority: Critical
>
> Using Wildfly 14.0.1.Final
> When deploying inter-app-appA.war, Wildfly complains about the EJB lookup for:
> @ejb(lookup = "java:global/inter-app-appB/BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar")
> Likewise, when deploying inter-app-appB.war, Wildfly complains about the EJB lookup for:
> @ejb(lookup = "java:global/inter-app-appA/FooImpl!org.jboss.as.quickstarts.interapp.shared.Foo")
> To reproduce, from the inter-app quickstart:
> mvn install wildfly:deploy
> Can also reproduce by just doing an mvn install, then manually deploying the jar, then appA, then appB using the HAL Management Console.
> {noformat}
> ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "inter-app-appA.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"]
> }
> 09:56:51,014 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "inter-app-appA.war" was rolled back with the following failure message:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"]
> }
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11210) inter-app can't be deployed
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11210?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11210:
-----------------------------------------
[~emmartins] See the discussion on WFLY-11084. This is not a valid app design, due to the circular dependencies, or at least it is not if you are not willing to do all management of the apps via composite managment ops (e.g. CLI batch.) And if you're always going to have to manage the apps as a unit, a technology like an ear seems like a better practice. Since I think part of the point of the QS is to not use an ear, and it seems like a bad idea to promote something that requires a CLI batch, I think the thing to do is to get rid of the circular dependencies.
Since this is a JIRA for the QS component I am going to reject the other one, as we are not going to change the server. Any QS change can be tracked by this.
> inter-app can't be deployed
> ---------------------------
>
> Key: WFLY-11210
> URL: https://issues.jboss.org/browse/WFLY-11210
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Jean-Francois Denise
> Assignee: Eduardo Martins
> Priority: Major
>
> When deploying we have un-resolved dependency.
> I am using jboss EAP quickstarts and wildfly 15.0.0.Alpha1-SNAPSHOT
> 16:45:57,040 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 3.0.5 (Final)
> 16:45:57,454 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "inter-app-appA.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"]
> }
> 16:45:57,457 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "inter-app-appA.war" was rolled back with the following failure message:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.inter-app-appA.inter-app-appA.env.\"org.jboss.as.quickstarts.interapp.appA.Imports\".bar is missing [jboss.naming.context.java.global.inter-app-appB.\"BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar\"]"]
> }
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (SWSQE-459) Speed up main pipeline (not including test parallelization)
by Guilherme Baufaker Rêgo (Jira)
[ https://issues.jboss.org/browse/SWSQE-459?page=com.atlassian.jira.plugin.... ]
Guilherme Baufaker Rêgo updated SWSQE-459:
------------------------------------------
Sprint: Kiali Sprint #12, Kiali Sprint #13 (was: Kiali Sprint #12)
> Speed up main pipeline (not including test parallelization)
> -----------------------------------------------------------
>
> Key: SWSQE-459
> URL: https://issues.jboss.org/browse/SWSQE-459
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Michael Foley
> Priority: Minor
>
> SWSQE-450 identified a few options how to speed up main pipeline:
> * Istio-and-Kiali-on-Openshift is not allowed to be run in parallel so it's the bottle neck right now -> run it in parallel but make sure it's not running concurrently on shared openshift cluster.
> * bookinfo installation takes ~6 minutes, it should be faster when done together with istio install in previous step if possible
> * Install Kiali takes ~9 minutes, we need to find out what is the longest part. e.g. if it's building it can be run in parallel with previous step (building does not need to wait for istio installation, only deploying has to)
> Note that this task is only to speed up the pipeline itself which will save a few minutes maximally. Another step will be to create multiple openshift clusters to be able run more pipelines concurrently.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months