[
https://issues.apache.org/jira/browse/SLING-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245694#comment-15245694
]
Ian Boston commented on SLING-5647:
-----------------------------------
[~mpetria].
For OOTB standalone no action is required.
For a dedicated ActiveMQ cluster, BROKER_URL needs to be set to point the the
instance.
For the Sling Instances to run as a embedded AMQ cluster, the AMQ cluster needs
to start with a local BrokerURL configuration, and an ActiveMQ configuration
file needs to be present or pointed to. I haven't implemented an OSGi property
to point to the configuration file. (yet).
Its just possible that using the standard ActiveMQ configuration files doesn't
work for Sling, in which case an alternative mechanism for provisioning the
embedded broker in multi master mode will need to be found.
> Provide ActiveMQ implementation of the MoM API in SLING-5646
> ------------------------------------------------------------
>
> Key: SLING-5647
> URL: https://issues.apache.org/jira/browse/SLING-5647
> Project: Sling
> Issue Type: Sub-task
> Reporter: Ian Boston
> Assignee: Ian Boston
>
> Provide a default implementation of the MoM API in SLING-5646 using ActiveMQ.
> The bundle must create and start a running ActiveMQ server without additional
> intervention and configuration. Ideally the bundle should work in a cluster
> embedding an ActiveMQ broker into each Sling instance, and ideally the bundle
> should be able to integrate with an existing ActiveMQ cluster. Based on AMQ
> documentation all are possible via configuration and no code changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
