| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IBM XMS parallel processing |
« View previous topic :: View next topic » |
| Author |
Message
|
| drajani |
 Posted: Wed Dec 21, 2016 3:17 am Post subject: IBM XMS parallel processing |
 |
|
Newbie
Joined: 21 Dec 2016
Posts: 9
|
I need to process each message only once - order is not important. For a given queue Q1, to achieve better throughput, I am planning to do as below from C# based application (IBM MQ v8, XMS v2.5)
- Establish single connection.
- Create 5 (configurable) tasks - one transacted session per task.
- Every session's message consumer listens to Q1.
- In OnMessage, session committed after each message processing is successful. If processing fails, session is rolled back and message moved to backout queue.
I would like to confirm below -
1. Does above approach makes sense to achieve higher throughput.
2. Is it guaranteed that each message will be received on only one of the 5 sessions? Could not find relevant documentation if this is a supported behavior. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 21, 2016 5:13 am Post subject: Re: IBM XMS parallel processing |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| drajani wrote: |
I need to process each message only once - order is not important. For a given queue Q1, to achieve better throughput, I am planning to do as below from C# based application (IBM MQ v8, XMS v2.5)
- Establish single connection.
- Create 5 (configurable) tasks - one transacted session per task.
- Every session's message consumer listens to Q1.
- In OnMessage, session committed after each message processing is successful. If processing fails, session is rolled back and message moved to backout queue.
I would like to confirm below -
1. Does above approach makes sense to achieve higher throughput.
2. Is it guaranteed that each message will be received on only one of the 5 sessions? Could not find relevant documentation if this is a supported behavior. |
#1 Yes you will get higher throughput. Remember to set the sharecvn (1) to get the best throughput.
Session rollback and backout to backout queue / dead letter queue is supposed to be automatic in XMS (i.e. behaves like JMS and you don't have to code for it!
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| drajani |
| Posted: Wed Dec 21, 2016 7:48 pm Post subject: |
|
|
Newbie
Joined: 21 Dec 2016
Posts: 9
|
Thanks for your reply. I will check on sharecvn. Agreed separate code is not required for rollback scenarios.
Is #2 a expected behavior ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 22, 2016 2:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| drajani wrote: |
Thanks for your reply. I will check on sharecvn. Agreed separate code is not required for rollback scenarios.
Is #2 a expected behavior ? |
yes it is. Remember that you are expected to directly consume the message and not try to browse it first. Let the system handle all of the locking aspects.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| drajani |
| Posted: Thu Dec 22, 2016 3:25 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2016
Posts: 9
|
|
| 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
|
|
|
|
