JMS XA/ASF Swiftlet: consumer-prefetch-size removed.
2 posts in topic
Flat View  Flat View
Older Post First |   Reply to Topic
TOPIC ACTIONS:
 

Posted By:   Jason_Dillon
Posted On:   Monday, June 17, 2002 12:50 PM

Does this mean that it is no longer possible to control the number of prefetched messages for a consumer? Or has this been moved to a different config? One of the reasons we wanted to move to SwiftMQ is because it supported the ability to limit the number of prefetched messages. We were planning on setting this to 1, so that multipule consumers across many machines can better share the load of messages, with out stavation due to a large prefetched consumer queue (which JBossMQ does). With 3.2.0 is it still possible to control this? Or have I mis-interprested the change notes somehow? Thanks, --jason    More>>

Does this mean that it is no longer possible to control the number of prefetched messages for a consumer? Or has this been moved to a different config?


One of the reasons we wanted to move to SwiftMQ is because it supported the ability to limit the number of prefetched messages. We were planning on setting this to 1, so that multipule consumers across many machines can better share the load of messages, with out stavation due to a large prefetched consumer queue (which JBossMQ does).


With 3.2.0 is it still possible to control this? Or have I mis-interprested the change notes somehow?


Thanks,


--jason

   <<Less
Report | Quote This | Send private message | Reply | Print

Re: JMS XA/ASF Swiftlet: consumer-prefetch-size removed.

Posted By:   Andreas_Mueller  
Posted On:   Monday, June 17, 2002 01:28 PM

There are docs available ;-) on this issue:


http://www.swiftmq.com/products/router/swiftlets/jms/index.html


Scroll down, CONNECTION FACTORIES.
Report | Quote This | Send private message | Reply | Print

Re: JMS XA/ASF Swiftlet: consumer-prefetch-size removed.

Posted By:   Andreas_Mueller  
Posted On:   Monday, June 17, 2002 01:22 PM

SwiftMQ 3.2.0 introduces consumer caches not only for connection consumers but for all consumers, therefore the consumer-prefetch-size was superfluous.

The cache size can be configured through the connection factories. That's also new in 3.2.0. Connection factories are located below the JMS listener. The default consumer cache size is 500 messages. You can change it or define your own connection factory.

You should remove the resp. JNDI aliases QueueConnectionFactory/TopicConnectionFactory and define connection factories with that names instead.
Report | Quote This | Send private message | Reply | Print
About | Sitemap | Contact