Bug 1282380 - "Address in use" exception thrown when running server after Cluster configuration
"Address in use" exception thrown when running server after Cluster configura...
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Installer (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: CR1
: 6.2.0
Assigned To: Thomas Hauser
Dominik Hanak
Depends On:
  Show dependency treegraph
Reported: 2015-11-16 04:15 EST by Dominik Hanak
Modified: 2015-11-25 05:23 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Full-logs from startup (1012.46 KB, text/plain)
2015-11-16 04:15 EST, Dominik Hanak
no flags Details

  None (edit)
Description Dominik Hanak 2015-11-16 04:15:10 EST
Created attachment 1094787 [details]
Full-logs from startup

Description of problem:
When I run "domain.sh" after installing product with Clustered configuration performed by Installer. Address already in use esception is thrown and server is started with errors.

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

How reproducible:

Steps to Reproduce:
1. Run installer
2. Install with Clustered Configuration
3. Run "startCluster.sh"
4. Run "domain.sh"

Actual results:
Exception is thrown and server startup fails.

Expected results:
No exception is thrown and server starts up sucesfully

Additional info:
The configuration from xml files is used and not ignored. Also when I check the ports declared in xml's, I see them free so the exception must come from Cluster somehow incorrectly managing communication between Git repos of zookeeper.
Comment 5 Dominik Hanak 2015-11-25 05:23:31 EST
After several attempts I was unable to reproduce this error again (Maybe it is cluster sometimes racing over Git ports (?), but I am not sure).

Both BRMS and BPMS start up the server successfully after cluster configuration done by Installer and mentioned Exception is not present. Thus, marking as verified in CR1.

Note You need to log in before you can comment on or make changes to this bug.