[
https://issues.apache.org/jira/browse/AMQ-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821227#comment-13821227
]
Bhanu commented on AMQ-4867:
----------------------------
Hi Gary,
Thanks for your response and explanation.
I need to monitor both the brokers. The monitoring team has provided us with
Client APIs which initializes and establishes a connection with the monitoring
server and does its heartbeating or whatever thing. Our both and primary and
failover brokers run under extremely critical production environment and we
*need* to *aggressively* monitor *even* the *failover* broker. Since if it goes
down, we want to be notified at the earliest and take appropriate steps.
That said we have a bunch of other ideas that we might want to implement via
plugins and they again involve both the brokers.
> Plugins do not get initialized in a failover broker until it takes over
> -----------------------------------------------------------------------
>
> Key: AMQ-4867
> URL: https://issues.apache.org/jira/browse/AMQ-4867
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.9.0
> Environment: linux
> Reporter: Bhanu
>
> Hi,
> We have a requirement where we want to initialize a plugin in the failover
> broker. The problem is that the plugin is not initialized until the failover
> broker takes over and becomes primary. Can some configuration be added to
> make this work ?
> Thanks & Regards,
> Bhanu
--
This message was sent by Atlassian JIRA
(v6.1#6144)
