Re: Test harness to verify Message Order Preservation

2012-08-21 Thread sk92129
So far I have tried to put a wait(2000) in the preProcessDispatch: @Override public void preProcessDispatch(MessageDispatch messageDispatch) { String contentStr = new String(messageDispatch.getMessage().getContent().getData()); if (pauseThisMsg(conte

Re: Pausing messages consuming

2012-08-21 Thread sk92129
I would like to jump into this thread and ask a related question. I would like to pause message from being consumed selectively, meaning that I would like to pause message #2 and #4. But all messages to be consumed. And then let message #2 and #4 to be consumed later. I think this would create

Re: Test harness to verify Message Order Preservation

2012-08-21 Thread sk92129
My thoughts on this : 1.) For the test harness activeMQ brokers, install an Interceptor based on BrokerFilter. http://activemq.apache.org/interceptors.html Install my interceptor into the broker. On inspection of the accessible methods on BrokerFilter, I am not sure which methods would allow my

Test harness to verify Message Order Preservation

2012-08-15 Thread sk92129
Hi, I am looking into how to build a configuration and verify a test that preserves JMS message order, as describe in the camel features below: http://activemq.apache.org/exclusive-consumer.html http://activemq.apache.org/message-groups.html The basic requirements for message order preservation

Re: activemq-admin stop does not work on Windows 7 pro

2012-07-31 Thread sk92129
3:02 AM, gtully [via ActiveMQ] wrote: > The admin commands use jmx to connect to the broker so you may need to > specify the jmx url, --jmxurl and verify that jmx remove access is > enabled > > http://activemq.apache.org/jmx.html > > > On 31 July 2012 01:01, sk92129 <[hidd

activemq-admin stop does not work on Windows 7 pro

2012-07-30 Thread sk92129
I am using Windows 7 Pro with activeMq 5.6.0. After I start up the broker with activemq.bat, I was testing to shut it down, using activemq-admin stop and activemq-admin stop --all This does not seem to work. On the console where I invoked activemq-admin stop (or with the --all) option, i see