Bug 1198932
Summary: | Quickstart deployment error | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Ryan Zhang <rzhang> | ||||
Component: | Quickstarts | Assignee: | Bill Rainford <brainfor> | ||||
Status: | CLOSED EOL | QA Contact: | Tomas David <tdavid> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 6.1.0 | CC: | kverlaen, rrajasek, rzhang | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-27 20:05:03 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1200413 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Ryan Zhang
2015-03-05 06:47:36 UTC
Ryan, I can not reproduce the issue with BPM Suite Business Central ER6 on EAP 6.4.0.ER3. This is the output of the server, everything looks fine: 10:46:13,772 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (http-localhost.localdomain/127.0.0.1:8080-1) KieModule was added: MemoryKieModule[releaseId=org.jboss.quickstarts.brms:decision-table-kmodule:1.0.0] 10:46:14,272 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (EJB default - 1) Computed the following DeltaSpike ProjectStage: Production 10:46:15,426 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EJB default - 1) KieModule was added: MemoryKieModule[releaseId=org.jboss.quickstarts.brms:bpms_project:1.0.0] 10:46:18,304 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EJB default - 1) KieModule was added: MemoryKieModule[releaseId=org.jboss.quickstarts.brms:helloworld-brms-kmodule:1.0.0] 10:46:21,447 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EJB default - 1) KieModule was added: MemoryKieModule[releaseId=org.jboss.quickstarts.brms:my-store-brms-kmodule:1.0.0] 10:46:21,448 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (EJB default - 1) KieModule was added: MemoryKieModule[releaseId=org.jboss.quickstarts.brms:helloworld-brms-kmodule:1.0.0] 10:46:22,724 INFO [org.uberfire.ext.metadata.io.BatchIndex] (EJB default - 1) Completed indexing of default://master@qs/ Could you provide some additional info on how to reproduce this? Created attachment 999829 [details]
server.log
I also can not reproduce the issue. I tried it on BPMS ER3 and ER2. Sorry. I tried it with BPMS ER6 on EAP 6.4.0.ER3 and EAP 6.4.0.ER2. The issue _seems_ to be related to the fact that the projects in the quickstarts repo have inter dependencies. For example decision-table-kmodule depends on helloworld-brms-kmodule. In case the decision-table-kmodule is built first (which it is) then it will fail, because its dependency (helloworld-brms-kmodule) was not yet built. The reason why this was passing for me was that I had the helloworld-brms-kmodule built from previous runs, so the BC was able to pick it up from local Maven repo (~/.m2). I am not really sure what we can do here. One solution would be to make the Business Central smart enough to figure out the inter dependencies and then build the projects in correct order. I created new BZ about the build order issues for BC: https://bugzilla.redhat.com/show_bug.cgi?id=1200413 I think that is currently the only correct way to solve this issue. (In reply to Tomas David from comment #5) > Sorry. I tried it with BPMS ER6 on EAP 6.4.0.ER3 and EAP 6.4.0.ER2. (In reply to Petr Siroky from comment #6) > The issue _seems_ to be related to the fact that the projects in the > quickstarts repo have inter dependencies. For example decision-table-kmodule > depends on helloworld-brms-kmodule. In case the decision-table-kmodule is > built first (which it is) then it will fail, because its dependency > (helloworld-brms-kmodule) was not yet built. The reason why this was passing > for me was that I had the helloworld-brms-kmodule built from previous runs, > so the BC was able to pick it up from local Maven repo (~/.m2). > > I am not really sure what we can do here. > > One solution would be to make the Business Central smart enough to figure > out the inter dependencies and then build the projects in correct order. (In reply to Tomas David from comment #5) > Sorry. I tried it with BPMS ER6 on EAP 6.4.0.ER3 and EAP 6.4.0.ER2. As Petr stated, this issue needs to clean the quickstarts jar in local repo first which is located in ${local-repo}/org/jboss/quickstarts/brms/*. (In reply to Petr Siroky from comment #6) > The issue _seems_ to be related to the fact that the projects in the > quickstarts repo have inter dependencies. For example decision-table-kmodule > depends on helloworld-brms-kmodule. In case the decision-table-kmodule is > built first (which it is) then it will fail, because its dependency > (helloworld-brms-kmodule) was not yet built. The reason why this was passing > for me was that I had the helloworld-brms-kmodule built from previous runs, > so the BC was able to pick it up from local Maven repo (~/.m2). > > I am not really sure what we can do here. > > One solution would be to make the Business Central smart enough to figure > out the inter dependencies and then build the projects in correct order. (In reply to Petr Siroky from comment #7) > I created new BZ about the build order issues for BC: > https://bugzilla.redhat.com/show_bug.cgi?id=1200413 > > I think that is currently the only correct way to solve this issue. OK, Thanks for your analyses. I put it in depends on. The actual reason for the error is slightly different from the one I described in comment #6. The build order is OK. However, after cloning the repo, BC will start indexing + building the projects (internally as they won't appear in ~/.m2 nor in bin/repositories/). One of the modules depends on another which is not available. The build then fails. This is the root cause, the CNFE seen later are caused by this. I am looking if we can fix this somehow quickly and without big changes. |