[jira] [Commented] (AMQ-4867) Plugins do not get initialized in a failover broker until it takes over
[ https://issues.apache.org/jira/browse/AMQ-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823470#comment-13823470 ] Bhanu commented on AMQ-4867: Thanks Gary, Probably for now I'll contend with initializing the monitoring client in a separate bean (not the plugin way) before the persistent adapters block the broker. > 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)
[jira] [Commented] (AMQ-4867) Plugins do not get initialized in a failover broker until it takes over
[ https://issues.apache.org/jira/browse/AMQ-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821251#comment-13821251 ] Gary Tully commented on AMQ-4867: - Can you wire the monitoring heartbeats to a JMX operation? JMX mbean server is started before we start the persistence adapter so you can query the brokerView Mbean. The isSlave attribute will reflect the current state of the failover broker. > 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)
[jira] [Commented] (AMQ-4867) Plugins do not get initialized in a failover broker until it takes over
[ 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)
[jira] [Commented] (AMQ-4867) Plugins do not get initialized in a failover broker until it takes over
[ https://issues.apache.org/jira/browse/AMQ-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821166#comment-13821166 ] Gary Tully commented on AMQ-4867: - what is this plugin doing? A slave broker blocks on creating the persistence adapter which is typically locked by the master. When the persistence adapter starts then it starts the broker, pluigns and transport/network connectors. The idea is that a client can only connect to a broker when it is started and has exclusive access to the store. So any plugin will not be able to do much b/c the broker can't do much. You could init your plugin as a spring bean and have it created when the context is loaded but maybe a plugin is not the way to go. Please provide some more context on what you are trying to achieve and why two instances of your plugin logic need to coexist. > 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)
[jira] [Commented] (AMQ-4867) Plugins do not get initialized in a failover broker until it takes over
[ https://issues.apache.org/jira/browse/AMQ-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821061#comment-13821061 ] Sophia Wright commented on AMQ-4867: I am also using Master/Slave configuration for ActiveMQ broker and faced the similar issue. Is there a way to initialize the plugin for failover broker ? > 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)
