----Original Message---- From: Ross Mason ross.mason@symphonysoft.com Sent: Tuesday, November 15, 2005 6:48 PM To: user@mule.codehaus.org Subject: RE: [mule-user] Jms connector - IBM MQ We actually don't support throttling at the moment. Can you raise an issue for this? One Workaround is to use the quartz transport to schedule a "receive" on the mq endpoint at your desired throttling pace. Have a look at the Jobs available in http://mule.codehaus.org/Quartz+Provider;

---

Ross Mason SymphonySoft www.symphonysoft.com Malta (GMT+1) Tel: +356 21 575 067 Fax: +356 21 575 067 Mob: +356 99 575 067 UK (GMT) Tel: +44 7005 978 001 Fax: +44 7005 978 003 Skype: rossjmason -------------------------------------------------------------------------------- From: Loka, Murlidhar Murlidhar_Loka@medco.com Sent: 15 November 2005 14:25 To: user@mule.codehaus.org Subject: [mule-user] Jms connector - IBM MQ I tried configuring the threading-profile and pooling-profile on the jms endpoint as well as the mule-environment with all values set to 1. Even with the above setting I am unable to get control or throttle the incoming messages being read from MQ Queue by the jms end point. Is there any additional configuration that needs to be done so that the MQ Queue is not drained of all the messages and we can throttle the message flow? Thanks, Loka. ============================================ This is a major drawback for us - even though there might be a workaround - would be nice if this functionality is provided by Mule API.