Bug 1009028 - Business central in cluster cannot be redeployed
Summary: Business central in cluster cannot be redeployed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER4
: 6.0.0
Assignee: Maciej Swiderski
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-17 14:16 UTC by Radovan Synek
Modified: 2014-08-06 20:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:10:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
node one server log (267.22 KB, text/x-log)
2013-09-17 14:16 UTC, Radovan Synek
no flags Details
node two server log (319.42 KB, text/x-log)
2013-09-17 14:16 UTC, Radovan Synek
no flags Details

Description Radovan Synek 2013-09-17 14:16:18 UTC
Created attachment 798836 [details]
node one server log

Attempt for redeploy of business central in cluster ended up with "Operation failed or was rolled back on all servers". Server logs contain exceptions with root cause:
org.apache.helix.HelixException: instance nodeOne_12345 already has a liveinstance in cluster jbpm-cluster

Version-Release number of selected component (if applicable):
BPMS-6.0.0.ER3

Steps to Reproduce:
1. configure cluster with 2 nodes
2. deploy business central
3. undeploy business central
4. deploy business central again => operation failed, see server logs

Attaching server logs from both nodes - containing useful information

Comment 1 Radovan Synek 2013-09-17 14:16:54 UTC
Created attachment 798837 [details]
node two server log

Comment 2 Radovan Synek 2013-09-17 14:24:19 UTC
To make it clear - there is a workaround - to stop & destroy the cluster completely, create it again and deploy business central once more. But this can be hardly final solution.

Comment 4 Radovan Synek 2013-10-17 13:47:27 UTC
Verified on BPMS-6.0.0.ER4


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