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

Bug 1059128

Summary: kie-config-cli fails after start if business-central is running on the same host
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: Maciej Swiderski <mswiders>
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: medium    
Version: 6.0.0CC: kverlaen
Target Milestone: ER1   
Target Release: 6.0.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:03:54 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
stacktrace none

Description Radovan Synek 2014-01-29 08:54:28 UTC
Created attachment 856963 [details]
stacktrace

Description of problem:
kie-config-cli fails with "java.net.BindException: Address already in use" right after start if it has been started on machine with running business-central. The problem is very likely caused by port conflict of git and ssh daemon. Because first thing kie-config-cli asks is location of git system repository (with ssh protocol), the only option should be to run this tool on different host to avoid port conflict.

Of course there is a workaround, for example to edit kie-config-cli.sh and set java parameters as follows:
JAVA_PARAMS="-Dorg.uberfire.nio.git.daemon.port=9419 -Dorg.uberfire.nio.git.ssh.port=8002"

On the other hand, user should not have to find workarounds for the first use of this tool. Moreover, I don't understand why it tries to start these git & ssh deamons if it should connect to those running in context of business-central.

Version-Release number of selected component (if applicable):
BPMS-6.0.0.CR2 (and probably also earlier)

Steps to Reproduce:
1. start business-central in default configuration
2. run kie-config.cli.sh

Comment 1 Maciej Swiderski 2014-01-30 18:41:41 UTC
actually the daemons should be disabled for kie-config-cli, so it is done with this fix

there was single, cumulative commit for recent issues with kie-config-cli as separate commits would make it more difficult due to extensive changes

kie-wb-distributions
master:
https://github.com/droolsjbpm/kie-wb-distributions/commit/b383c49db9f0b4b341fb9bbbe964f2300885602f

6.0.x:
https://github.com/droolsjbpm/kie-wb-distributions/commit/653cbff5720f5138c91eb47c9d6aef7f1ab1a086

Comment 2 Radovan Synek 2014-02-19 18:36:06 UTC
Verified with BPMS-6.0.1.ER1