[
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)
