Bug 1282380
| Summary: | "Address in use" exception thrown when running server after Cluster configuration | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Dominik Hanak <dhanak> | ||||
| Component: | Installer | Assignee: | Miroslav Sochurek <msochure> | ||||
| Status: | CLOSED EOL | QA Contact: | Dominik Hanak <dhanak> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 6.2.0 | CC: | rrajasek, rzhang | ||||
| Target Milestone: | CR1 | ||||||
| Target Release: | 6.2.0 | ||||||
| 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:00:41 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: |
|
||||||
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. |
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): 6.2.0 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.