Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1275703

Summary: AssetMgmt: Branches not set up completely when creating managed repository
Product: [Retired] JBoss BRMS Platform 6 Reporter: Jiri Locker <jlocker>
Component: Business CentralAssignee: Mauricio Salatino <msalatin>
Status: CLOSED NOTABUG QA Contact: Jiri Locker <jlocker>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.0CC: jlocker, kverlaen, mswiders
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: 2015-11-10 18:58:40 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:
Attachments:
Description Flags
server.log none

Description Jiri Locker 2015-10-27 14:11:14 UTC
Created attachment 1086858 [details]
server.log

Description of problem:
This only happens in BRMS, not in BPM Suite. After creating managed repository with a single project and automatically configured branches (master/dev/release), only dev branch is created and two exceptions can be found in server log:

* IllegalArgumentException: Unknown Command implemenation with name 'org.guvnor.asset.management.backend.command.CreateBranchCommand'

* IllegalStateException: There is no runtime manager for deployment org.guvnor:guvnor-asset-mgmt-project:6.3.0.Final-redhat-2

Version-Release number of selected component (if applicable):
6.2.0.ER4

How reproducible:
BRMS, asset management

Steps to Reproduce:
1. Log in with kie-mgmt role, go to Administration.
2. Create a managed repository, single project, automatically configured branches.

Actual results:
Only dev branch created, exceptions in server.log

Expected results:
dev and release branches created, no exceptions.

Additional info:

Comment 1 Mauricio Salatino 2015-11-03 13:10:26 UTC
I couldn't reproduce this one in 6.3.x kie-drools-wb (which is the base for BRMS). Branches are created correctly.

Comment 3 Mauricio Salatino 2015-11-04 12:08:29 UTC
@jlocker can you help me to reproduce this issue? I've created the distribution war for wildfly8 from the 6.3.x branch and this is working as expected in KIE-DROOLS-WB.

Comment 4 Jiri Locker 2015-11-04 13:36:59 UTC
Hi Mauricio, no change in ER5, I observe the same result.

However, I've found out that it doesn't happen when kie-server.war is NOT deployed. Is that helpful? May be related to bz 1265709.

Comment 5 Mauricio Salatino 2015-11-05 08:58:48 UTC
Really? so when kie-server.war is not deployed everything works as expected? 
I have no idea what is happening there.. I never imagine to test it with the kie-server.war deployed at the same time, it is not something that we do normally to reproduce issues. It might be the case that the kie-server is interfering with the branch creation or even with the process execution.

Comment 6 Maciej Swiderski 2015-11-09 17:00:23 UTC
correct, kie server and workbench should use different data bases/schemas to avoid this kind of issues. Since both do provide async execution behavior sharing same data store won't be efficient as they will potentially take jogs they should not take like guvnor commands etc. So defining independent data bases/schemas for both execution servers will solve the issue.

Comment 7 Kris Verlaenen 2015-11-10 12:52:27 UTC
Jiri, could you possibly check if this is indeed the issue so we can close this?

Comment 8 Jiri Locker 2015-11-10 18:58:40 UTC
Yes, the problem doesn't occur if kie-server.war is not deployed.