| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| transaction managerment with clusters |
« View previous topic :: View next topic » |
| Author |
Message
|
| vivekkooks |
 Posted: Tue Jul 15, 2003 6:39 am Post subject: transaction managerment with clusters |
 |
|
Voyager
Joined: 11 Jun 2003
Posts: 91
|
Hello,
Can we use MQSeries cluster in transaction management with database.
The scenario will be as follows:
There will be cluster of 3 MQ Managers(QM1,QM2,QM3).
all queue managers are installed on different systems(Linux/Intel).
QM2 and QM3 will contain cluster queues.
QM1 will be used as transaction manager for database. It will use cluster queues to put the messages to QM2 and QM3.
thanks |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Tue Jul 15, 2003 7:35 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Clustered queues are NO different than regular pre-defined queues. And hence you can do your transaction stuff on clustered queues as well. Make sure you are using BIND_NOT_FIXED, since you are trying to open and put to queues hosted on Qm2 and Qm3.
Also no Gets.
And transaction should be atomic. All the puts and db activity should be clubbed in one single transaction.
I myself have never come accross this, but i believe if you backout a put on a clustered queue, the message should be removed from the destination queue hosted on a different QM as it happens for a local pre-def queue. But someone from the list could confirm this, if tested it.
Cheers
Kumar |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Jul 15, 2003 1:02 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Kumar,
I think you are mistaken in your last statment. You said:
| Quote: |
| but i believe if you backout a put on a clustered queue, the message should be removed from the destination queue hosted on a different QM as it happens for a local pre-def queue |
The fact is, the message never actually gets sent across the network to the destination queue manager until the transaction is committed. It will sit on the SYSTEM.CLUSTER.TRANSMIT.QUEUE until the MQCMIT has been issued. I also believe the workload balancing algorithm determines which instance of the clustered queue to send the message to at the time of the MQPUT. So let's say you have Q1 on QM1 and QM2. You are on QM3, and (under syncpoint) put 2 messages to Q1. Assuming you have bind_not_fixed set, after the 2 MQPUTs, you'll have 2 messages on the SYSTEM.CLUSTER.TRANSMIT.QUEUE, and the transmission header for 1 of them will indicate it is bound for QM1, while the other message is bound for QM2. Then, when you issue the commit, both messages will flow.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Jul 15, 2003 2:38 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Ooops... Silly me.. What was i thinking...
Brandon you are right. I guess drug-effect is still on me(had a surgery recently).... :).
Thanks for correcting though.
Cheers
Kumar |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Jul 15, 2003 3:44 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
No problem... That's funny because your response reminds me of a time not too long ago when I posted something here that was completely wrong, and it was right after I had my wisdom teeth pulled out and I was on a ton of pain killers. Guess there's a reason why they say not to operate heavy machinery on the medicine bottles 
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| 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
|
|
|
|
