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 API Support » Implementing a write lock on a message

Post new topic  Reply to topic Goto page Previous  1, 2
 Implementing a write lock on a message « View previous topic :: View next topic » 
Author Message
fjb_saper
PostPosted: Thu Oct 12, 2006 3:48 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
Sure but without some fancy work you still have the problem of checkout for modification with pending lock?

What you describe here is a lazy update. The app trying to update has no idea whether it overwrites a previous config change or not.

You could of course request the update message to have the timestamp of the read (which would be the timestamp of the last update). Compare that with the timestamp of the current config record and if there is a discrepancy reject the update returning current state...

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Thu Oct 12, 2006 3:58 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
fjb_saper wrote:
Sure but without some fancy work you still have the problem of checkout for modification with pending lock?


Yeah. But I wouldn't consider adding a "read with lock" request message to be fancy work. A "read with lock" request message would instruct the server to change it's next GET to match either the same message ID or correlID or some such to ensure that it only handles the next message from the same client. Kind of a bi-directional request/reply.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Oct 12, 2006 3:25 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
jefflowrey wrote:
fjb_saper wrote:
Sure but without some fancy work you still have the problem of checkout for modification with pending lock?


Yeah. But I wouldn't consider adding a "read with lock" request message to be fancy work. A "read with lock" request message would instruct the server to change it's next GET to match either the same message ID or correlID or some such to ensure that it only handles the next message from the same client. Kind of a bi-directional request/reply.


Can't do that. In the meantime there are some requesters out there that just want to see the current config. (it has been "checked out" but not updated yet...)...

Best thing might be something like subversion or any other version control system and forget MQ for this stuff...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » IBM MQ API Support » Implementing a write lock on a message
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.