Comments on: MQ Import Anti-Pattern: Multiple MQ Imports connecting to single pair of physical request/response queues http://blog.danzrobok.com/2008/11/06/mq-import-anti-pattern-multiple-mq-imports-connecting-to-single-pair-of-physical-requestresponse-queues/ Business Integration and SOA with an IBM WebSphere slant Tue, 17 Aug 2010 21:36:16 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: dan http://blog.danzrobok.com/2008/11/06/mq-import-anti-pattern-multiple-mq-imports-connecting-to-single-pair-of-physical-requestresponse-queues/comment-page-1/#comment-3772 dan Mon, 17 Nov 2008 16:23:30 +0000 http://blog.danzrobok.com/2008/11/06/mq-import-anti-pattern-multiple-mq-imports-connecting-to-single-pair-of-physical-requestresponse-queues/#comment-3772 The 'anti-pattern' is for how you design your WID module. When you create an Import/Export for an MQ queue you are creating server resources that will listen and process messages. You can get yourself into a scenario where you have multiple listeners inside the same ear listening to the same queues and things can blow up in your face :-) As for the 'One-queue-to-rule-them-all' it's usually caused by an overeager push to be as 'dynamic' as possible without considering the actual value (if any) of the routing mechanism. The ‘anti-pattern’ is for how you design your WID module. When you create an Import/Export for an MQ queue you are creating server resources that will listen and process messages. You can get yourself into a scenario where you have multiple listeners inside the same ear listening to the same queues and things can blow up in your face :-)

As for the ‘One-queue-to-rule-them-all’ it’s usually caused by an overeager push to be as ‘dynamic’ as possible without considering the actual value (if any) of the routing mechanism.

]]> By: Arnold http://blog.danzrobok.com/2008/11/06/mq-import-anti-pattern-multiple-mq-imports-connecting-to-single-pair-of-physical-requestresponse-queues/comment-page-1/#comment-3662 Arnold Fri, 14 Nov 2008 21:34:34 +0000 http://blog.danzrobok.com/2008/11/06/mq-import-anti-pattern-multiple-mq-imports-connecting-to-single-pair-of-physical-requestresponse-queues/#comment-3662 Not sure I follow the whole scenario but why not have more than one queue per service instead of this one queue handles all? Not sure I follow the whole scenario but why not have more than one queue per service instead of this one queue handles all?

]]>