| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQClient with MQBACK / MQCMIT over distributed system |
« View previous topic :: View next topic » |
| Author |
Message
|
| lyntongrice |
 Posted: Mon Apr 15, 2013 11:35 am Post subject: MQClient with MQBACK / MQCMIT over distributed system |
 |
|
Acolyte
Joined: 26 Sep 2010
Posts: 70
|
Hi there,
Currently I have an application written in C running on the SAME server as Websphere MQ. I do NOT need to support XA transactions, all I need to do is ensure that I can rollback / commit messages with the queue manager.
Now I would like to move my application to ANOTHER server and use the MQ Client lib instead of the MQ server lib .....BUT still have the same solid MQBACK etc over the geographically distributed solution
Question is, is the only real advantage having an application running on the SAME server as the MQ queue manager that I can use XA transactions with DB2 etc?
Can I have reliable rollback / commits if my MQ client application is running in say Brazil and the queue manager is in Spain? I am assuming so......but just wanted to double check with the guru's to make 100% sure....
Thanks for the help
Lynton |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 15, 2013 12:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You are going to be subject to the aleas of communications
Do you consider the transaction committed if it committed on the qmgr but the communication broke before the client got notified ?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Apr 15, 2013 5:41 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Moving from local server binding to remote client will have the same functionality for MQCMIT / MQBACK.
Client introduces additional points of failure and uncertainty. The main concern is that the TCP session could fail due to a network issue during a call to MQCMIT or MQBACK. The call will return to the client app with MQRC_CONNECTION_BROKEN and there is no easy way to determine if the syncpoint actually committed or not. Are you willing to accept this risk? The client app may run for years without ever experiencing this scenario.
The same caveat applies to server binding, but the window is orders of magnitude smaller.
_________________
Glenn |
|
| Back to top |
|
|
| lyntongrice |
| Posted: Tue Apr 16, 2013 9:10 am Post subject: |
|
|
Acolyte
Joined: 26 Sep 2010
Posts: 70
|
Hi there,
Many thanks for the information, much appreciated 
I have just learned than my app will be running in a VM on the SAME physical machine as MQ.....so the possibility of the network getting broken will also be pretty small......at least I hope so
Thanks again
Lynton |
|
| 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
|
|
|
|
