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

Bug 1274569

Summary: org.uberfire.cluster.autostart for cluster configuration
Product: [Retired] JBoss BRMS Platform 6 Reporter: Toshiya Kobayashi <tkobayas>
Component: DocumentationAssignee: brms-docs <brms-docs>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1.0CC: alazarot, brms-docs, tradej
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 22831, Installation Guide-6.1 Build Date: 31-07-2015 13:58:58 Topic ID: 22894-762514 [Latest]
Last Closed: 2020-03-27 19:04:57 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:

Description Toshiya Kobayashi 2015-10-23 02:15:52 UTC 
Title: Configuring Clustering on Red Hat JBoss EAP

Describe the issue:

The example configurations (Example 5.5. Cluster nodeOne configuration, Example 5.6. Cluster nodeTwo configuration, Example 5.7. Cluster nodeThree configuration) set the system property "org.uberfire.cluster.autostart" to "true".

===
<property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/>
===

But it causes an issue described in BZ1271898. "false" is the correct value.

As the default value is "false", we can simply remove the line from the configuration.

Comment from Alexandre Porcelli:
===
Today for BxMS there isn’t a case for org.uberfire.cluster.autostart to ‘true'

Anyway… we’re working on this for 7, so we expect to have a different infra for clustering (it means a way simpler infra!).
===

Suggestions for improvement:

Remove <property name="org.uberfire.cluster.autostart" value="true" boot-time="true"/> from the configurations.