Yes , the client is running as a separate process from the broker . based on
what you said , i have to expose the broker service as an mbean which can
run on the broker machine and through JMX i have to get that mbean and
associated region broker.
--
View this message in context:
http://active
In our production environment, we use AMQ broker with Kaha DB persistence. We
have set the following in broker configuration:
schedulePeriodForDestinationPurge="60"
offlineDurableSubscriberTimeout="25920"
offlineDurableSubscriberTaskSchedule="360"
Sometimes, I have observed that whe
Is your already-running broker running in the same process as your client?
Or are you trying to interact with a broker that's in a separate process?
If the latter, I don't think what you're trying to do will work; you should
see whether the JMX API (which will work with a separate process) will mee