ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » MQ msgs sent to MDB's in clustered Websphere app servers

Post new topic  Reply to topic
 MQ msgs sent to MDB's in clustered Websphere app servers « View previous topic :: View next topic » 
Author Message
david lightman
PostPosted: Sun Sep 03, 2006 5:42 am    Post subject: MQ msgs sent to MDB's in clustered Websphere app servers Reply with quote

Newbie

Joined: 03 Sep 2006
Posts: 3

When implementing a system what uses Websphere MQ for messaging infrastructure, thick java clients are able to send transactions(MQ messages) that are sent to a websphere application server to be processed by MDB's that subsequently pass the tran to biz service & eventually calls DAO layer for DB2 update. however, some of these message from the client must be kept in a strict order to be processed. I would like to have connection pooling on the MDB's so they can process all the messages concurrently, not just have set certain mdb's to MAX session = 1. What is the best solution for this scenario, has anyone else seen this where you must have strict message order but want to send to a was cluster that process concurretly? spinning these particular trans that must be kept in order off to separate system such as a msg broker? to be grouped etc... then passed to WAS?

thoughts anyone?
thanks
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Sep 03, 2006 6:03 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Usually, people design MQ systems to avoid message affinity - particularly when you need to spread them out over a large infrastructure.

What business justification is presented for requiring messages to be processed in a particular order?

Is it expected that you need to preserve message affinity across messages coming from multiple clients? Or just each client? If you only need to preserve the logical order of messages from a single client, then grouping is what you need. If you need to preserve logical order across multiple clients, then you're in for a big fun time.

Go back to the business requirements, and see if they can be met without requiring message affinity. Particularly look at what "should" happen if the *user* presents the messages in the wrong order.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » MQ msgs sent to MDB's in clustered Websphere app servers
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.