Bug 724287 (BRMS-232) - Requesting support for Drools Guvnor in a clustered environment
Summary: Requesting support for Drools Guvnor in a clustered environment
Keywords:
Status: VERIFIED
Alias: BRMS-232
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Configuration
Version: 5.0.0 GA
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: GA
: BRMS 5.2.0.GA
Assignee: Julian Coleman
QA Contact: Len DiMaggio
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-01 13:30 UTC by Len DiMaggio
Modified: 2021-04-09 12:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-232 0 Major Closed Requesting support for Drools Guvnor in a clustered environment 2013-11-12 01:54:51 UTC

Internal Links: 744216

Description Len DiMaggio 2009-10-01 13:30:27 UTC 
securitylevel_name: Public

Platform JIRA for project JIRA:  JBRULES-2286
Comment 1 Len DiMaggio 2009-10-01 13:32:17 UTC 
Link: Added: This issue depends JBRULES-2286
Comment 2 Alessandro Lazarotti 2011-09-27 14:26:36 UTC 
Tihomir, was not it done by your drools-ant task?
http://planet.jboss.org/post/configuring_multiple_guvnor_instances_in_a_jackrabbit_cluster


What is the next step for this to be supported on BRMS product?
Comment 3 Alessandro Lazarotti 2011-10-07 13:37:40 UTC 
Ok, after talk to Tihomir by IRC I see that Jackrabbit cluster is just a part to cluster BRMS product. We need certify the product in a cluster environment (load balance/ failover) including different app servers. Finally is necessary build a documentation about this to delivery a full supportable product.
Comment 5 Lukáš Petrovický 2012-05-02 12:41:49 UTC 
Clustering in Guvnor has been verified working with BRMS 5.2.
Note You need to log in before you can comment on or make changes to this bug.