| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| grouping with msgBroker then passing to WAS to ensure order |
« View previous topic :: View next topic » |
| Author |
Message
|
| teal |
 Posted: Mon Jan 23, 2006 3:24 pm Post subject: grouping with msgBroker then passing to WAS to ensure order |
 |
|
Acolyte
Joined: 15 Dec 2004
Posts: 66
|
Im totally new to this WMsgbroker, but here goes...
right now I lower the max session for an MDB listener so it will only process the msgs in order, however i was told it could could possible solve issues I have in designing a system that must ensure message are kept in order. -That the WMB can group them and them pass them on the WAS mdb's ensuring order allowing me to cluster the WAS instances, (right now its not possible because the msgs would get out of order if it sent to all different queues out of order)
any thoughts?
thank you |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Jan 23, 2006 3:33 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I am new to message broker too, but there are aggregate nodes that might be helpful to you.
But, firstly, I think atleast you need to clearly explain the situation you are in.
What kind of messages are you getting
How do you expect to identify a group.... based on what etc |
|
| Back to top |
|
|
| teal |
| Posted: Mon Jan 23, 2006 3:40 pm Post subject: |
|
|
Acolyte
Joined: 15 Dec 2004
Posts: 66
|
thanks for the reply.
clients send two types of messages, persist/nonpersist
nonpersist we can care less if they are out of order so on those MDBs we use connection pooling to process msgs concurrently however the persist ones must be always processed in order. Im brainstorming on a way to have the persistMDBs also to have the ability to use connection pooling so I was thinking that a WMB could organize them so they could never get out of order and ensure specific types of persist trans are grouped before passing them on to the was mdbs.
I apologize if i am still confusing. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jan 23, 2006 5:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The aggregate nodes aren't going to help.
Aggregate nodes let you accumulate a closed set of messages (for example, messages 1-5). It seems like you've got an open set of messages - every persistant message.
I think you're going to have to ensure that you can hold messages that are out of sequence until the proper time - that is, ensure that you always process message N only after message N-1 has shown up, and hold message N+1 until later.
And you'll have to write code to do this. I don't think grouping will help either - as the best grouping will give you is "wait until messages x to y are here", not "wait until message N+1 is here".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
