[overlord-issues] [JBoss JIRA] (BAM-113) BAM should work in a clustered JBossAS environment

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/BAM-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751042#comment-12751042 ] 

Gary Brown commented on BAM-113:
--------------------------------

Documentation has been updated to include the new common config location $JBOSS_HOME/standalone/configuration/overlord-bam.properties, which includes the default infinispan container JNDI name to use. If running clustered config, then this property should be uncommented, and an explicit entry should be created under this default 'cluster' container for each cache. The one used to test the policy enforcement example was:

{noformat}
            <cache-container name="cluster" aliases="ha-partition" default-cache="default">
                <transport lock-timeout="60000"/>
                <replicated-cache name="default" mode="SYNC" batching="true">
                    <locking isolation="REPEATABLE_READ"/>
                </replicated-cache>
                <replicated-cache name="Principals" mode="SYNC">
                    <locking isolation="REPEATABLE_READ"/>
                    <transaction mode="FULL_XA" locking="PESSIMISTIC"/>
                </replicated-cache>
            </cache-container>
{noformat}
                
> BAM should work in a clustered JBossAS environment
> --------------------------------------------------
>
>                 Key: BAM-113
>                 URL: https://issues.jboss.org/browse/BAM-113
>             Project: Business Activity Monitoring
>          Issue Type: Task
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>            Priority: Critical
>             Fix For: 1.0.0.M4
>
>
> Current version works in a standalone server. Need to ensure that it can also work in a clustered environment. Areas to check:
> (1) JMS event distribution - ensure event processor work is distributed across multiple servers without problem, and that all servers are notified of results to update their local active collection representations.
> (2) When caching used in support of the event processing and/or active collections, ensure that caches are correctly configured to work in the cluster.
> (3) CEP configuration to work in a cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira