activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Levy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3368) Patch to disable all endpoints
Date Wed, 15 Jun 2011 16:53:48 GMT

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

Jeremy Levy updated AMQ-3368:
-----------------------------

    Attachment: ActiveMQResourceAdapter_Disable_All_Endpoints.txt

> Patch to disable all endpoints 
> -------------------------------
>
>                 Key: AMQ-3368
>                 URL: https://issues.apache.org/jira/browse/AMQ-3368
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JCA Container
>         Environment: n/a
>            Reporter: Jeremy Levy
>            Priority: Minor
>         Attachments: ActiveMQResourceAdapter_Disable_All_Endpoints.txt
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> For packaging scenarios where MDB endpoints are deployed along with EJB's and WARs in
an EAR but you don't want the queues to be activated on some servers this patch provides a
system property that allows you to disabled endpoint activation.
> Setting the system property 'activemq.endpoints.disabled' to true will stop queues from
activating.   For example: 
> java -Dactivemq.endpoints.disabled=true -jar myjar.jar 
> This is useful if you want to keep your deployment archive the same across multiple instances
but reserve some servers for queue processing.  The exclusive consumer functionality isn't
sufficient incase you want to have multiple MDBs active.
> See email thread titled "Patch to disable all Queues" on users@activemq.apache.org from
6/1/2011 for more details.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message