JConsole has an MBeans tab for viewing the JMX beans for the app it attaches to, and you can drill down to the topic and then see what consumers are attached to it. You might take a look there to see if there are any consumers attached that you're not aware of, or any durable subscriptions for consumers who are offline. You can also look clientConnectors->openwire->clientId at the root of your broker and see what clients have connected (I think it shows prior connections and current ones together) to see who's connected to that backup host...
On Thu, Oct 2, 2014 at 11:46 AM, pwalter <patrick.wal...@nasa.gov> wrote: > There were no topics when the clients started. > At startup the primary has consumers but secondary does not. > For each publish request the numbers of Enqueued message values increase on > both primary and secondary servers. > I'm using the randomize=false option, so what is causing secondary to even > be involved until the primary is not available. > thanks again!! > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Backup-Server-Failover-tp4686109p4686111.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
