Author |
Message
|
rathnak |
Posted: Wed Nov 28, 2018 7:18 am Post subject: Suppress error message related to a particular object |
|
|
 Newbie
Joined: 01 Feb 2014 Posts: 7
|
Hello Masters,
i am in a situation wherein an MQ client doesnt work as expected. as requested by the application team, we stopped the svrconn channel to not let the app read the messages out of a queue.
Doing this actually triggers qmgr error logs and it is rapid. i need to suppress/exclude errors related to this particular svrconn channel. is there a way to do that?
i am aware that from qm.ini, we can suppress error messages with the AMQ code or we can set the qmgr to record the logs once in certain interval. doing this would suppress errors related to other channels too. i dont want this to happen. kindly let me know if there is a way? or any other ideas?
Thanks,
Dante |
|
Back to top |
|
 |
Vitor |
Posted: Wed Nov 28, 2018 7:23 am Post subject: Re: Suppress error message related to a particular object |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rathnak wrote: |
Doing this actually triggers qmgr error logs and it is rapid. |
What errors? You should get something saying the channel's been stopped but that should be it.
Also why stop the SVRCONN channel? Why not Get Disable the queue in question? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
rathnak |
Posted: Wed Nov 28, 2018 7:27 am Post subject: |
|
|
 Newbie
Joined: 01 Feb 2014 Posts: 7
|
yes, and the application actually tries to access the channel frequently. this keeps the error logs recording
Also why stop the SVRCONN channel? Why not Get Disable the queue in question?
-->thats what the app team needs. they need the svrconn to be stopped during when they fix it(not sure for how long). i suggested to disable get on the local queue. but they dont need it. instead they need the channel to be down.  |
|
Back to top |
|
 |
Vitor |
Posted: Wed Nov 28, 2018 7:52 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rathnak wrote: |
yes, and the application actually tries to access the channel frequently. this keeps the error logs recording |
It shouldn't. The application should get a 2059 and (possibly) an error in their client log.
What error are you seeing in the queue manager log? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Nov 28, 2018 7:55 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rathnak wrote: |
Vitor wrote: |
Also why stop the SVRCONN channel? Why not Get Disable the queue in question? |
-->thats what the app team needs. they need the svrconn to be stopped during when they fix it(not sure for how long). i suggested to disable get on the local queue. but they dont need it. instead they need the channel to be down.  |
Your app team are lucky to have such a tolerant MQ admin. They would have got a very different reaction from me. Along with some unkind comments about their problem resolution strategy.
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|