Mixing
IBM MQ client is unable to reconnect to MQ server intermittently
Context:
We have built a Windows service in C#.NET (4.5). The service listens to IBM MQ (ver: IBM Websphere MQ 8.0.0.6) 24 X 7 and picks up the message for processing when it’s available.
The MQ server goes down every Sunday for maximum duration of 6 hours. To handle this, we have set WMQ_CLIENT_RECONNECT_OPTIONS property as WMQ_CLIENT_RECONNECT and WMQ_CLIENT_RECONNECT_TIMEOUT to 28800 while creating connection. This means we are asking MQ client to try reconnecting automatically for 8 hours.
We have also registered a callback function to handle Connection exception. We keep on getting following log every second or so while MQ is down:
MQ delivered an asynchronous event with completion code 0, and reason 2544.
As soon as the MQ server is up we also get following exception:
MQ delivered an asynchronous event with completion code 0, and reason 2545.
Problem:
As stated above, the MQ server goes down every Sunday for maximum duration of 6 hours. Generally, MQ client (.NET service) is able to reconnect but on some occasions the client is not able to reconnect. We are getting same logs even when client is not able to reconnect to MQ. We don’t get any special exception as well.
Questions:
- What could be potential issues?
- Are we missing any property?
- Is something missing in MQ server configuration?
.net windows-services connection ibm-mq
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
asked Nov 22 '18 at 13:44
ram shahram shah
1
add a comment |
Context:
We have built a Windows service in C#.NET (4.5). The service listens to IBM MQ (ver: IBM Websphere MQ 8.0.0.6) 24 X 7 and picks up the message for processing when it’s available.
The MQ server goes down every Sunday for maximum duration of 6 hours. To handle this, we have set WMQ_CLIENT_RECONNECT_OPTIONS property as WMQ_CLIENT_RECONNECT and WMQ_CLIENT_RECONNECT_TIMEOUT to 28800 while creating connection. This means we are asking MQ client to try reconnecting automatically for 8 hours.
We have also registered a callback function to handle Connection exception. We keep on getting following log every second or so while MQ is down:
MQ delivered an asynchronous event with completion code 0, and reason 2544.
As soon as the MQ server is up we also get following exception:
MQ delivered an asynchronous event with completion code 0, and reason 2545.
Problem:
As stated above, the MQ server goes down every Sunday for maximum duration of 6 hours. Generally, MQ client (.NET service) is able to reconnect but on some occasions the client is not able to reconnect. We are getting same logs even when client is not able to reconnect to MQ. We don’t get any special exception as well.
Questions:
- What could be potential issues?
- Are we missing any property?
- Is something missing in MQ server configuration?
.net windows-services connection ibm-mq
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
asked Nov 22 '18 at 13:44
ram shahram shah
1
Reason code 2544(MQRC_RECONNECTING) and 2545 (MQRC_RECONNECTED) are expected. Reason code 2544 sent back to application callback to indicate MQ .NET client is attempting to reconnect to queue manager. What reason code your application receives when it fails to reconnect? Have you checked if your queue manager is up before the reconnection timeout?
– Shashi
Nov 22 '18 at 14:04
Do you get the 2545 even when it fails to reconnect?
– JoshMc
Nov 22 '18 at 17:31
add a comment |
Context:
We have built a Windows service in C#.NET (4.5). The service listens to IBM MQ (ver: IBM Websphere MQ 8.0.0.6) 24 X 7 and picks up the message for processing when it’s available.
The MQ server goes down every Sunday for maximum duration of 6 hours. To handle this, we have set WMQ_CLIENT_RECONNECT_OPTIONS property as WMQ_CLIENT_RECONNECT and WMQ_CLIENT_RECONNECT_TIMEOUT to 28800 while creating connection. This means we are asking MQ client to try reconnecting automatically for 8 hours.
We have also registered a callback function to handle Connection exception. We keep on getting following log every second or so while MQ is down:
MQ delivered an asynchronous event with completion code 0, and reason 2544.
As soon as the MQ server is up we also get following exception:
MQ delivered an asynchronous event with completion code 0, and reason 2545.
Problem:
As stated above, the MQ server goes down every Sunday for maximum duration of 6 hours. Generally, MQ client (.NET service) is able to reconnect but on some occasions the client is not able to reconnect. We are getting same logs even when client is not able to reconnect to MQ. We don’t get any special exception as well.
Questions:
- What could be potential issues?
- Are we missing any property?
- Is something missing in MQ server configuration?
.net windows-services connection ibm-mq
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
asked Nov 22 '18 at 13:44
ram shahram shah
1
Context:
We have built a Windows service in C#.NET (4.5). The service listens to IBM MQ (ver: IBM Websphere MQ 8.0.0.6) 24 X 7 and picks up the message for processing when it’s available.
The MQ server goes down every Sunday for maximum duration of 6 hours. To handle this, we have set WMQ_CLIENT_RECONNECT_OPTIONS property as WMQ_CLIENT_RECONNECT and WMQ_CLIENT_RECONNECT_TIMEOUT to 28800 while creating connection. This means we are asking MQ client to try reconnecting automatically for 8 hours.
We have also registered a callback function to handle Connection exception. We keep on getting following log every second or so while MQ is down:
MQ delivered an asynchronous event with completion code 0, and reason 2544.
As soon as the MQ server is up we also get following exception:
MQ delivered an asynchronous event with completion code 0, and reason 2545.
Problem:
As stated above, the MQ server goes down every Sunday for maximum duration of 6 hours. Generally, MQ client (.NET service) is able to reconnect but on some occasions the client is not able to reconnect. We are getting same logs even when client is not able to reconnect to MQ. We don’t get any special exception as well.
Questions:
- What could be potential issues?
- Are we missing any property?
- Is something missing in MQ server configuration?
.net windows-services connection ibm-mq
.net windows-services connection ibm-mq
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
asked Nov 22 '18 at 13:44
ram shahram shah
1
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
asked Nov 22 '18 at 13:44
ram shahram shah
1
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
edited Nov 22 '18 at 16:35
JoshMc
5,6341624
5,6341624
asked Nov 22 '18 at 13:44
ram shahram shah
1
asked Nov 22 '18 at 13:44
ram shahram shah
1
asked Nov 22 '18 at 13:44
ram shahram shah
1
1
Reason code 2544(MQRC_RECONNECTING) and 2545 (MQRC_RECONNECTED) are expected. Reason code 2544 sent back to application callback to indicate MQ .NET client is attempting to reconnect to queue manager. What reason code your application receives when it fails to reconnect? Have you checked if your queue manager is up before the reconnection timeout?
– Shashi
Nov 22 '18 at 14:04
Do you get the 2545 even when it fails to reconnect?
– JoshMc
Nov 22 '18 at 17:31
add a comment |
Reason code 2544(MQRC_RECONNECTING) and 2545 (MQRC_RECONNECTED) are expected. Reason code 2544 sent back to application callback to indicate MQ .NET client is attempting to reconnect to queue manager. What reason code your application receives when it fails to reconnect? Have you checked if your queue manager is up before the reconnection timeout?
– Shashi
Nov 22 '18 at 14:04
Do you get the 2545 even when it fails to reconnect?
– JoshMc
Nov 22 '18 at 17:31
Reason code 2544(MQRC_RECONNECTING) and 2545 (MQRC_RECONNECTED) are expected. Reason code 2544 sent back to application callback to indicate MQ .NET client is attempting to reconnect to queue manager. What reason code your application receives when it fails to reconnect? Have you checked if your queue manager is up before the reconnection timeout?
– Shashi
Nov 22 '18 at 14:04
Reason code 2544(MQRC_RECONNECTING) and 2545 (MQRC_RECONNECTED) are expected. Reason code 2544 sent back to application callback to indicate MQ .NET client is attempting to reconnect to queue manager. What reason code your application receives when it fails to reconnect? Have you checked if your queue manager is up before the reconnection timeout?
– Shashi
Nov 22 '18 at 14:04
Do you get the 2545 even when it fails to reconnect?
– JoshMc
Nov 22 '18 at 17:31
Do you get the 2545 even when it fails to reconnect?
– JoshMc
Nov 22 '18 at 17:31
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432347%2fibm-mq-client-is-unable-to-reconnect-to-mq-server-intermittently%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432347%2fibm-mq-client-is-unable-to-reconnect-to-mq-server-intermittently%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Reason code 2544(MQRC_RECONNECTING) and 2545 (MQRC_RECONNECTED) are expected. Reason code 2544 sent back to application callback to indicate MQ .NET client is attempting to reconnect to queue manager. What reason code your application receives when it fails to reconnect? Have you checked if your queue manager is up before the reconnection timeout?
– Shashi
Nov 22 '18 at 14:04
Do you get the 2545 even when it fails to reconnect?
– JoshMc
Nov 22 '18 at 17:31