| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Anyways to see the message content when queue is inhibited? |
« View previous topic :: View next topic » |
| Author |
Message
|
| shashivarungupta |
 Posted: Thu May 12, 2011 4:49 am Post subject: |
 |
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| mqjeff wrote: |
| Or temporarily redirect the message routing to a different queue.... |
Yup, I have a wild guess that OP is developing some message flow (probably using message set) and wanted to check that msg that's coming to the queue is correct or not, but seems he has deployed the flow and applications are having handle on the queue too (may be on 'test' server)
I could be wrong too !
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu May 12, 2011 6:44 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Some folks use Alias queues for everything, and this scenario is one of the big benefits. If you force an Alias queue between the app and the actual local queue it listens to, you can get disable the Alias queue, which keeps the consuming app from grabbing the messages, but allows you to go to the actual local queue and have a look.
At first glance it seems like a lot of extra queues to be building an Alias queue for every new queue, but is sure can come in handy. When it comes to MQ security in clusters and on z/OS, there are some scenarios that can only be solved by Alias queues.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 12, 2011 7:41 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| PeterPotkay wrote: |
At first glance it seems like a lot of extra queues to be building an Alias queue for every new queue, but is sure can come in handy. |
QAlias is my personal recommendation best-practice.
I recommend to clients that all new queues have QAliases; and that the programmers only be given the QAlias name, and never the real underlying queue name.
QAliases provide a level of abstraction from the real underlying queue. As such, it gives administrators on all platforms great flexibility; and imposes no practical problems for developers.
The real local queue can have multiple QAliases. QAliases can have different security rules. QAliases can have different get/put enable/disable than the real underlying queue.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu May 12, 2011 8:37 am Post subject: Re: Anyways to see the message content when queue is inhibit |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| rekarm01 wrote: |
One way to accomplish this is to define a queue alias, with queue local as target queue, and get-inhibit the queue alias.
Apps that open the queue alias can't get/browse messages, but apps that open the queue local can. |
One drawback with get-inhibit though, is that complaining applications tend to clutter up various error logs.
An alternative (at least for Unix platforms) is to:- temporarily suspend the consuming process(es) using "kill -STOP pid(s)"
- and resume them at a later time using "kill -CONT pid(s)"
Other platforms may offer something similar. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 12, 2011 8:59 am Post subject: Re: Anyways to see the message content when queue is inhibit |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| rekarm01 wrote: |
One drawback with get-inhibit though, is that complaining applications tend to clutter up various error logs. |
If the queue is get-inhibited, MQGET call will return a ReasonCode to the application. How, or if, the application deals with a get-inhibited rc is up to the developer.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu May 12, 2011 1:52 pm Post subject: Re: Anyways to see the message content when queue is inhibit |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| bruce2359 wrote: |
| How, or if, the application deals with a get-inhibited rc is up to the developer. |
For many applications, (such as for WMB message flows), the developer is an external vendor; the customer may have little or no influence over how the application behaves.
Even when the application handles get-inhibit adequately, there may be various circumstances where it's not the best available option. For example, if the developer doesn't have authorization to get-inhibit a queue, but does have permission to suspend an application (or stop a message flow), then the latter options seem preferable.
However, setting up alias queues, and enabling/disabling them as needed is still a good option, and often the best option (for all the reasons stated earlier). It's just not the only option. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
