[ 
https://issues.apache.org/activemq/browse/SMX4KNL-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SMX4KNL-106.
-------------------------------------

         Assignee: Guillaume Nodet
    Fix Version/s: 1.1.0
       Resolution: Fixed

Adding         main/src/main/java/org/apache/servicemix/kernel/main/Lock.java
Sending        main/src/main/java/org/apache/servicemix/kernel/main/Main.java
Adding         
main/src/main/java/org/apache/servicemix/kernel/main/SimpleFileLock.java
Transmitting file data ...
Committed revision 701077.

> Support for container level lock to support master/slave deployments
> --------------------------------------------------------------------
>
>                 Key: SMX4KNL-106
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-106
>             Project: ServiceMix Kernel
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>         Environment: 4.x
>            Reporter: Dave Stanley
>            Assignee: Guillaume Nodet
>             Fix For: 1.1.0
>
>
> Using an approach similar to ServiceMix 3,  its possible to use ActiveMQ's 
> persistence adapter locking to setup master (ACTIVE) and slave (STANDBY) 
> container instances. This requires changing the manifest in the bundle jar 
> generated for the ActiveMQ broker, to set "create-asynchronously:=false" and 
> setting the run level for activemq such that its the first application bundle 
> deployed, e.g.
> {code}
> Manifest-Version: 2
> Import-Package: javax.transaction,org.apache.activemq,org.apache.activ
>  emq.pool,org.springframework.beans.factory.config
> Spring-Context: *;publish-context:=false;create-asynchronously:=false
> Bundle-SymbolicName: localhost-broker.xml
> Bundle-Version: 0.0.0
> DynamicImport-Package: *
> {code}   
> While this handles HA for message's flowing through the container, it would 
> be nice if the locking could be done at the container level. 
> This is an enhancement request to support locking the slave and master on the 
> same <ESB>/data directory. Ideally the locking should be handled by a lock 
> adapter such that both file level & jdbc/DB based locking can be supported.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to