I guess we could add a useAsyncSubscribe flag to the connection. You just have to be aware that the subscribe could fail and that it would produce and error that you can catch using an ExceptionListener registered with the connection.
On 8/9/06, James Strachan <[EMAIL PROTECTED]> wrote:
On 8/9/06, Danilo Tuler <[EMAIL PROTECTED]> wrote: > Hi, > > My call to ActiveMQSession.createConsumer is very slow, taking up to 2 > seconds to responde. That sounds like a slow internet link - or maybe the broker is overworked? > The client and server are separated by an internet connection. > The broker is being fed by a single producer on the same machine of the > broker. > > Debugging the client code I see AMQ sends a synchronous message to the > broker with the ConsumerInfo. And this is blocking the client. My > application needs to subscribe to ~50 topics, but taking more than a minute > to do that is unacceptable for me. > > Is this performance normal? No - its very slow > Is there any tweak or test I could make? Pretty much all request-responses with the broker are about the same in terms of time. > Do you need any more info on my configuration? > > My debug call stack is below. You could try subscribe to many destinations in one go using composite destinations... http://incubator.apache.org/activemq/composite-destinations.html other than that all you can do is investigate your network/hardware/firewall/proxies to see why request-response over your network is so slow -- James ------- http://radio.weblogs.com/0112098/
-- Regards, Hiram Blog: http://hiramchirino.com
