| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| RFE to allow browsing of uncommitted messages on a queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Fri Jan 03, 2014 4:11 am Post subject: RFE to allow browsing of uncommitted messages on a queue |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I've submitted an RFE to allow (optionally) browsing of uncommitted messages on a local queue.
Please vote early and often!
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=43287
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Jan 03, 2014 4:58 am Post subject: Re: RFE to allow browsing of uncommitted messages on a queue |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| zpat wrote: |
| Please vote early and often! |
Perhaps this might be safer to implement to only allow a browse of uncomitted messages if the user is authorized at an MQ Administrator level, i.e. a member of the mqm group. This request is similiar to the one I opened a while back asking to allow an MQ Administrator the ability to browse a get inhibited queue. Both of these RFEs are to allow an MQ Admin to do their job faster and easier. An MQ Admin should be able to do things apps can't (browse uncomitted messages; browse inhibited queues).
"Just use trace" is not good enough - a trace imparts to much overhead, is difficult to read and doesn't help to review what's already on the queue from before the trace was started.
If I could get the data via trace, then there is no reason to not make it easier for us to get the data by directly browsing the queue using our favorite MQ Admin tools, as long as its implemented in a manner that is backwards compatible and that doesn't break the once-and-only-once assured delivery model.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Jan 03, 2014 6:30 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Possibly, although it would also be useful to developers and other non mqm users.
If necessary an additional OAM access check could be made to a queue name like SYSTEM.BROWSE.UNCOM to see if the option is permitted when opening the queue.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| 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
|
|
|
|
