| Author |
Message
|
| billybong |
 Posted: Mon Jun 23, 2008 1:53 am Post subject: Changing MAX message priority on qmgr [solved] |
 |
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
Is there a way to change the max allowed MQ priority on the queue manager? We've ended up with messages that exceeds the maximum allowed which seems to cause problems with our broker flows.
Or, could I reset them all on the messages somehow?
Need advice asap if someone knows how.
Thanks guys!
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower
Last edited by billybong on Tue Jun 24, 2008 1:04 am; edited 1 time in total |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon Jun 23, 2008 2:01 am Post subject: Re: Changing MAX message priority on qmgr |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| billybong wrote: |
Is there a way to change the max allowed MQ priority on the queue manager? We've ended up with messages that exceeds the maximum allowed which seems to cause problems with our broker flows.
Or, could I reset them all on the messages somehow?
Need advice asap if someone knows how.
Thanks guys! |
1. Why the messages are getting piled up?
2. why its not getting feeded up?
3. setting priority should be taken care very carefully
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| billybong |
| Posted: Mon Jun 23, 2008 2:19 am Post subject: |
|
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
I dont know why the broker fails to read the messages, but after deploying flows that sets the priority to 0 and starting them no messages are picked up by the broker.
The priority was set by a sloppy broker developer (me... :-/)
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 23, 2008 3:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| billybong wrote: |
I dont know why the broker fails to read the messages, but after deploying flows that sets the priority to 0 and starting them no messages are picked up by the broker.
The priority was set by a sloppy broker developer (me... :-/) |
You have to be careful when setting the priority. A 0 priority means the lowest priority. Messages not getting picked up is not necessarily a bad thing. It might just mean that the flow instances are busy with messages with higher priority and don't get to those with lower priority...
So check whether the EG is running the flow, whether the flow is active and doing work and finally whether adding instances of the flow(scaling) will solve your problem 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| billybong |
| Posted: Tue Jun 24, 2008 1:01 am Post subject: |
|
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
I found a solution to my problem.
With MQMON you can always unload the messages to a file and then use a text editor with a regexp search/replace and replace all
A PRI .+?
with
A PRI 0
Then you simply load the messages back again.
Didn't know it was that simple to change MQ headers with MQmon and a text editor. Might probably come in handy later on.
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Jun 24, 2008 1:04 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
do you agree that this is a good solution. its only a work around and a temperory fix.
its better if you do it logically so it wont happen or make you to change it manually.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| billybong |
| Posted: Tue Jun 24, 2008 11:09 pm Post subject: |
|
|
Disciple
Joined: 22 Jul 2005
Posts: 150
Location: Stockholm, Sweden
|
Yes, its a fix for the messages that got stuck on the queues.
In order to fix the priorities being too high you of course have to redesign the flow, which I also did.
But the problem was that the messages got "stuck", and that fixed itself by lowering their priority value.
_________________
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Integration Developer V6.0
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere DataPower |
|
| Back to top |
|
|
|
|
