{"id":410,"date":"2012-06-14T08:08:39","date_gmt":"2012-06-14T13:08:39","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/06\/rockerduck-increased-messages-in-queue\/"},"modified":"2012-06-14T08:08:39","modified_gmt":"2012-06-14T13:08:39","slug":"rockerduck-increased-messages-in-queue","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/06\/rockerduck-increased-messages-in-queue\/","title":{"rendered":"ROCKERDUCK Increased Messages in Queue"},"content":{"rendered":"<p>Over the past week we\u2019ve noticed a larger than normal queue size on ROCKERDUCK. On our Exchange servers we strive to keep queues under 50 message at any given time which roughly equates to about 1-5 seconds of delivery time. However this week we received alerts from our monitoring of queues reaching 150 messages and staying rather \u201clarge\u201d for the entire day. The larger queue size would only increase delivery time to 15-30 seconds, but was still above our desired values. Upon researching and testing we\u2019ve discovered the root issue. <\/p>\n<p>Microsoft has an undocumented\/secret new XML value for Hub servers which limits the number of concurrent deliveries for a mailbox that appeared in SP1 that you can only find by searching the error from the delivery queue. <\/p>\n<p><a href=\"http:\/\/blogs.technet.com\/b\/exchange\/archive\/2011\/04\/11\/store-driver-fault-isolation-improvements-in-exchange-2010-sp1.aspx\">http:\/\/blogs.technet.com\/b\/exchange\/archive\/2011\/04\/11\/store-driver-fault-isolation-improvements-in-exchange-2010-sp1.aspx<\/a> <\/p>\n<p>Essentially since SP1 the HUB servers were only allowed one current message delivery per recipient <\/p>\n<p>We\u2019ve increased the delivery from 1 concurrent delivery to 3 concurrent deliveries and have not received any new alerts. <\/p>\n<p>Travis Sheldon<br \/>VP, Network Operations, ExchangeDefender<br \/>(877) 546-0316 x757<br \/>travis@ownwebnow.com<\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-410","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=410"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/410\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}