Occasionally my client (with discovery turned on) will get the onServiceRemove method called even though the broker that has supposedly gone away is still connected and functioning properly. What causes these erroneous onServiceRemove calls, and is there a way to double check to make sure that we are still connected to a broker? -- View this message in context: http://www.nabble.com/Random-onServiceRemove-calls-even-though-broker-still-connected.-tp25351189p25351189.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
