| Author |
Message
|
| vmanel |
 Posted: Wed Apr 24, 2019 10:49 pm Post subject: IIB Publication Node failure |
 |
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
Hi,
We have a publication node in the iib message flow, which was working fine.
But we faced intermittent issue saying 'Failure occurred while putting message to Queue manager' with BIP 7122 error code
And after sometime it worked fine
And that issue occured for only 2 message flows which had same topic string, and all other flows with publication node were working fine
How to find what was the issue that occured, as I am not able to find any details in broker logs/QM logs
Thanks |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Thu Apr 25, 2019 1:08 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi...the broker log should've the MQ reason code as well which should then help in identifying what went wrong at MQ end.
'BIP7122
Failure occurred putting a message to the queue manager on topic <insert_2>. The WebSphere MQ reason code is <insert_1>.' |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 2:01 am Post subject: |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| abhi_thri wrote: |
hi...the broker log should've the MQ reason code as well which should then help in identifying what went wrong at MQ end.
'BIP7122
Failure occurred putting a message to the queue manager on topic <insert_2>. The WebSphere MQ reason code is <insert_1>.' |
Found the error code, it is 2502 |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 25, 2019 4:54 am Post subject: Re: IIB Publication Node failure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
We have a publication node in the iib message flow, which was working fine.
But we faced intermittent issue saying 'Failure occurred while putting message to Queue manager' with BIP 7122 error code
And after sometime it worked fine |
Locate the admin who was working on the affected queue manager during the time period of the failure.
Interrogate the admin who was working on the affected queue manager during the time period of the failure.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 6:17 am Post subject: Re: IIB Publication Node failure |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| Vitor wrote: |
| vmanel wrote: |
We have a publication node in the iib message flow, which was working fine.
But we faced intermittent issue saying 'Failure occurred while putting message to Queue manager' with BIP 7122 error code
And after sometime it worked fine |
Locate the admin who was working on the affected queue manager during the time period of the failure.
Interrogate the admin who was working on the affected queue manager during the time period of the failure. |
Can you please explain how this issue occurs, we faced this issue for few hours and after that it resolved automatically and that too for not all applications
Is it an intermittent issue? What does 2502 error code mean? Is it due to IIB or problem at MQ side? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 25, 2019 6:54 am Post subject: Re: IIB Publication Node failure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
| Can you please explain how this issue occurs, we faced this issue for few hours and after that it resolved automatically and that too for not all applications |
If you look up the description of that reason code, you'll find a couple of scenarios where this occurs. For this to be working, stop working and then start working again the likely cause is someone amending settings in a way that's not a good idea, realizing their mistake and changing them back.
| vmanel wrote: |
| Is it an intermittent issue? |
Depends if the admin realizes what's happening and fixes it.
| vmanel wrote: |
| What does 2502 error code mean? |
What the documentation explains that it means.
| vmanel wrote: |
| Is it due to IIB or problem at MQ side? |
It's an MQ issue. The clue is the MQ reason code. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 7:46 am Post subject: Re: IIB Publication Node failure |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| Vitor wrote: |
If you look up the description of that reason code, you'll find a couple of scenarios where this occurs. For this to be working, stop working and then start working again the likely cause is someone amending settings in a way that's not a good idea, realizing their mistake and changing them back.
Depends if the admin realizes what's happening and fixes it.
|
I can confirm that settings were not modified.
| Vitor wrote: |
| What the documentation explains that it means. |
From the documentation I understand that this issue occurs if the combination syncpoint and another attribute is modified, but what does that mean? We do not modify any such attributes and we create topic and subscription with default values
One more question is how IIB handles such failure, we have MQ input node as the starting point of the flow and target is publication node, does the message go to failure terminal or the catch terminal when this error occurs? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 25, 2019 8:42 am Post subject: Re: IIB Publication Node failure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
| I can confirm that settings were not modified. |
Reconcile this statement with
| vmanel wrote: |
| From the documentation I understand that this issue occurs if the combination syncpoint and another attribute is modified |
So you didn't modify any settings, but your own research indicates this happens when a setting is modified.
| vmanel wrote: |
| We do not modify any such attributes and we create topic and subscription with default values |
Not deliberately perhaps.
| vmanel wrote: |
| we have MQ input node as the starting point of the flow and target is publication node, does the message go to failure terminal or the catch terminal when this error occurs? |
See Handling errors in message flows and Handling MQ Input node errors.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 9:19 am Post subject: Re: IIB Publication Node failure |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
Because no one modifies anything in MQ without notifying us, so I am pretty sure and can assure that settings were not modified
One more thing is for input we are using a Queue Manager that is connecting to IIB as Client through MQ policy and output is published to a local Queue Manager(coupled with IIB). And we have observed some connectivity issues in this approach.
Do you think this can be a possible cause for this issue, if yes, then why did it affect only 2 flows with certain topic string and not other flows. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 25, 2019 10:07 am Post subject: Re: IIB Publication Node failure |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
| Because no one modifies anything in MQ without notifying us, so I am pretty sure and can assure that settings were not modified |
I admire your confidence in your associates and your change control process.
| vmanel wrote: |
One more thing is for input we are using a Queue Manager that is connecting to IIB as Client through MQ policy and output is published to a local Queue Manager(coupled with IIB). And we have observed some connectivity issues in this approach.
Do you think this can be a possible cause for this issue, |
No.
If it was a connectivity issue, you'd see a 2009/2019/2059 reason code or similar. This reason code is from the server side reporting that the publication could not be completed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 10:16 am Post subject: |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
Thanks!
Any other reason because of which this could have occurred or any suggestion to investigate it furthur? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 25, 2019 10:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vmanel wrote: |
| Any other reason because of which this could have occurred |
None springs to mind.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 10:44 am Post subject: |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| Thank you very much! You always help a lot! |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Thu Apr 25, 2019 3:12 pm Post subject: Re: IIB Publication Node failure |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| vmanel wrote: |
| But we faced intermittent issue saying 'Failure occurred while putting message to Queue manager' with BIP 7122 error code ... Found the [MQ] error code, it is 2502 |
The underlying issue occurred with a subscriber, not with the publisher: "delivery of the publication to one of the subscribers failed". The MQRC 2502 doesn't explain why the delivery failed; it only explains what the publisher chose to do about it.
The programmer can either "find the subscriber or subscribers who are having problems with their subscription queue and resolve the problem", or else change the Topic attributes, so that the publisher can ignore such problems. |
|
| Back to top |
|
|
| vmanel |
| Posted: Thu Apr 25, 2019 8:39 pm Post subject: Re: IIB Publication Node failure |
|
|
Acolyte
Joined: 12 Mar 2019
Posts: 57
|
| rekarm01 wrote: |
The underlying issue occurred with a subscriber, not with the publisher: "delivery of the publication to one of the subscribers failed". The MQRC 2502 doesn't explain why the delivery failed; it only explains what the publisher chose to do about it. |
How to find out why the delivery failed? We have subscriptions as remote queue pointing to another QM, could it be because of some connectivity issue with that? But only two subscriptions were affected with same topic string and all other subscriptions were working fine.
| rekarm01 wrote: |
| The programmer can either "find the subscriber or subscribers who are having problems with their subscription queue and resolve the problem", or else change the Topic attributes, so that the publisher can ignore such problems. |
No attributes of subscription or subscription queue were modified. What attribute are you referring to? |
|
| Back to top |
|
|
|
|
