Yes. What I meant is it does not support prefetch=0.
> -Original Message-
> From: James Green [mailto:james.mk.gr...@gmail.com]
> Sent: Friday, May 06, 2011 4:31 AM
> To: users@activemq.apache.org
> Subject: Re: Scaleability problems with queue subscriptors
>
> It
gs server side which would help with the
> scalability of concurrent subscribes?
>
> > -Original Message-
> > From: Gary Tully [mailto:gary.tu...@gmail.com]
> > Sent: Wednesday, May 04, 2011 5:39 PM
> > To: users@activemq.apache.org
> > Subject: Re: Scaleabi
04, 2011 5:39 PM
> To: users@activemq.apache.org
> Subject: Re: Scaleability problems with queue subscriptors
>
> have you tried to use prefetch=0 on the work queue, so the next
> message will not be dispatched till you issue another receive call
> rather than when the ack occurs
scale this given our current architecture?
>
> -Josh
>
>> -Original Message-
>> From: Gary Tully [mailto:gary.tu...@gmail.com]
>> Sent: Friday, April 29, 2011 6:27 PM
>> To: users@activemq.apache.org
>> Subject: Re: Scaleability problems with queue subscri
le to
scale this given our current architecture?
-Josh
> -Original Message-
> From: Gary Tully [mailto:gary.tu...@gmail.com]
> Sent: Friday, April 29, 2011 6:27 PM
> To: users@activemq.apache.org
> Subject: Re: Scaleability problems with queue subscriptors
>
> setting
setting up a consumer is a little expensive, have a look at using a
composite destination so that you can subscribe to all destinations at
once.
Also, there is a delay between new consumer registration and async
dispatch, so waiting a few seconds before unsubscribe is necessary.
http://activemq.ap
