mkeenan wrote:
>
>
> jfcharles wrote:
>>
>> The 2 forms of configuration reflect this, either assigned in the client
>> connection url or associated with a destination again configured by the
>> client.
>>
>
> Thanks for your response.
>
> To clarify my original post-- when I tried to set it in the client URL is
> not working for me. It does work on a per-destination setting. So my
> question was: Is there a mistake in my notation when trying to set it in
> the client URL for all destinations.
>
> The question about setting it at the broker level was more of a
> "workaround" since I couldn't get it working globally at the client level
> without setting it on each destination.
>
>
I see. The syntax looks fine to me. Perhaps write a simple Java client and
use the same connection parameters to see if there is a problem. If there is
then try against AMQ5.1. (I am pretty sure that version of AMQ will work).
If neither of those reveal a problem it looks like a problem in the NMS
library.
A bit of trial and error should isolate the problem.
John C.
--
View this message in context:
http://www.nabble.com/A-question-about-prefetch-with-NMS-tp20157793p20181828.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
