activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQNET-226) ?consumer.prefetchSize=X overrides message consumer in pull mode
Date Wed, 16 Dec 2009 13:49:53 GMT


Timothy Bish commented on AMQNET-226:

If I'm understanding this correctly then it looks ok to me.  The Destination allows you the
option of overriding the Prefetch policy settings on the Connection which should be considered
the defaults for all Consumers.  If you want a specific destination to have some other prefetch
value than you set the "?consumer.prefetchSize=5" option on the destination and it overrides
the defaults.  

What was the behaviour you were expecting?  

> ?consumer.prefetchSize=X overrides message consumer in pull mode
> ----------------------------------------------------------------
>                 Key: AMQNET-226
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Test
>          Components: NMS
>    Affects Versions: 1.2.0
>         Environment: ActiveMQ 5.2
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>             Fix For: 1.2.0
>         Attachments:
> Not sure if this is a bug or more of misconfiguration between broker and NMS.  But if
I set the prefetch policy queue prefetch to zero:
> ((Connection)_listenerConnection2).PrefetchPolicy = new PrefetchPolicy() { QueuePrefetch
= 0 };
> and configure my destination to prefetch 5:
> IDestination destination2 = new ActiveMQQueue(_queue + "?consumer.prefetchSize=5");
> When _listenerConnection2 pulls it prefetches five messages.  Should the prefetch config
on the destination be ignored?
> I've attached a test.  Run a producer and consumer at the same time sending 20 messages.
 This will actually run two consumers (one prefetch mode and the other pull mode).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message