Mixing
IBM MQ upgrade causing error 2059 and error 2018
0
In my application one interface is connected to external system on MQ. When MQ upgrade is performed by system team from MQ version 7.5 to version 8.0 we are facing error 2059 and error 2018. We could see the below error in our log file.
error from log :-
18.07.24 19:49:11 [mqseries:14610]mqs_process_mb_msg:**MQCONN ended with reason code 2059**
18.07.24 19:49:11 [mqseries:14610]mqs_exit: signal 0 received
18.07.24 19:49:11 [mqseries:14610]**ABST.ONLINE.PUT.DBSI.Q Disconnected**
18.07.24 19:49:11 [mqseries:14610]**MQCLOSE ABST.ONLINE.PUT.DBSI.Q ended with reason 2018**
18.07.24 19:49:11 [mqseries:14610]**MQDISC ended with reason code 2018**
Please note once the system team is downgrading it back to MQ version 7.5 it is working fine and as expected. Kindly help on what could be the missing during the MQ upgrade from version 7.5 to version 8.
c++ linux ibm-mq
edited Jan 2 at 14:50
JoshMc
5,6891625
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
add a comment |
0
In my application one interface is connected to external system on MQ. When MQ upgrade is performed by system team from MQ version 7.5 to version 8.0 we are facing error 2059 and error 2018. We could see the below error in our log file.
error from log :-
18.07.24 19:49:11 [mqseries:14610]mqs_process_mb_msg:**MQCONN ended with reason code 2059**
18.07.24 19:49:11 [mqseries:14610]mqs_exit: signal 0 received
18.07.24 19:49:11 [mqseries:14610]**ABST.ONLINE.PUT.DBSI.Q Disconnected**
18.07.24 19:49:11 [mqseries:14610]**MQCLOSE ABST.ONLINE.PUT.DBSI.Q ended with reason 2018**
18.07.24 19:49:11 [mqseries:14610]**MQDISC ended with reason code 2018**
Please note once the system team is downgrading it back to MQ version 7.5 it is working fine and as expected. Kindly help on what could be the missing during the MQ upgrade from version 7.5 to version 8.
c++ linux ibm-mq
edited Jan 2 at 14:50
JoshMc
5,6891625
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
What does the error log on the queue manager show? What specific v8.0.0.x do they upgrade to? What specific version is your MQ client?
– JoshMc
Jan 2 at 14:44
You only get 2018, because you are trying to close a connection not opened correctly. Your only error code seems to be 2059, wich suggests the QM isn’t actually running when “migrated”. Have you checked the QM error logs?
– Attila Repasi
Jan 2 at 17:06
MQ versions below for your reference:- $dspmqver -a Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Linux (x86-64 platform) Mode: 64-bit O/S: Linux 2.6.32-754.6.3.el6.x86_64 InstName: Installation1 InstDesc: Primary: Yes InstPath: /opt/mqm DataPath: /var/mqm MaxCmdLevel: 802 -------------------------------------------------------- $rpm -qa | grep MQSeriesClient MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8009-8.0.0-9.x86_64
– Syed Mudhasir
Jan 3 at 11:08
Both of us asked for what the QM error logs have, can you provide?
– JoshMc
Jan 6 at 2:53
add a comment |
0
0
0
In my application one interface is connected to external system on MQ. When MQ upgrade is performed by system team from MQ version 7.5 to version 8.0 we are facing error 2059 and error 2018. We could see the below error in our log file.
error from log :-
18.07.24 19:49:11 [mqseries:14610]mqs_process_mb_msg:**MQCONN ended with reason code 2059**
18.07.24 19:49:11 [mqseries:14610]mqs_exit: signal 0 received
18.07.24 19:49:11 [mqseries:14610]**ABST.ONLINE.PUT.DBSI.Q Disconnected**
18.07.24 19:49:11 [mqseries:14610]**MQCLOSE ABST.ONLINE.PUT.DBSI.Q ended with reason 2018**
18.07.24 19:49:11 [mqseries:14610]**MQDISC ended with reason code 2018**
Please note once the system team is downgrading it back to MQ version 7.5 it is working fine and as expected. Kindly help on what could be the missing during the MQ upgrade from version 7.5 to version 8.
c++ linux ibm-mq
edited Jan 2 at 14:50
JoshMc
5,6891625
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
In my application one interface is connected to external system on MQ. When MQ upgrade is performed by system team from MQ version 7.5 to version 8.0 we are facing error 2059 and error 2018. We could see the below error in our log file.
error from log :-
18.07.24 19:49:11 [mqseries:14610]mqs_process_mb_msg:**MQCONN ended with reason code 2059**
18.07.24 19:49:11 [mqseries:14610]mqs_exit: signal 0 received
18.07.24 19:49:11 [mqseries:14610]**ABST.ONLINE.PUT.DBSI.Q Disconnected**
18.07.24 19:49:11 [mqseries:14610]**MQCLOSE ABST.ONLINE.PUT.DBSI.Q ended with reason 2018**
18.07.24 19:49:11 [mqseries:14610]**MQDISC ended with reason code 2018**
Please note once the system team is downgrading it back to MQ version 7.5 it is working fine and as expected. Kindly help on what could be the missing during the MQ upgrade from version 7.5 to version 8.
c++ linux ibm-mq
c++ linux ibm-mq
edited Jan 2 at 14:50
JoshMc
5,6891625
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
edited Jan 2 at 14:50
JoshMc
5,6891625
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
edited Jan 2 at 14:50
JoshMc
5,6891625
edited Jan 2 at 14:50
JoshMc
5,6891625
edited Jan 2 at 14:50
JoshMc
5,6891625
5,6891625
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
asked Jan 2 at 12:26
Syed MudhasirSyed Mudhasir
36125
36125
What does the error log on the queue manager show? What specific v8.0.0.x do they upgrade to? What specific version is your MQ client?
– JoshMc
Jan 2 at 14:44
You only get 2018, because you are trying to close a connection not opened correctly. Your only error code seems to be 2059, wich suggests the QM isn’t actually running when “migrated”. Have you checked the QM error logs?
– Attila Repasi
Jan 2 at 17:06
MQ versions below for your reference:- $dspmqver -a Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Linux (x86-64 platform) Mode: 64-bit O/S: Linux 2.6.32-754.6.3.el6.x86_64 InstName: Installation1 InstDesc: Primary: Yes InstPath: /opt/mqm DataPath: /var/mqm MaxCmdLevel: 802 -------------------------------------------------------- $rpm -qa | grep MQSeriesClient MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8009-8.0.0-9.x86_64
– Syed Mudhasir
Jan 3 at 11:08
Both of us asked for what the QM error logs have, can you provide?
– JoshMc
Jan 6 at 2:53
add a comment |
What does the error log on the queue manager show? What specific v8.0.0.x do they upgrade to? What specific version is your MQ client?
– JoshMc
Jan 2 at 14:44
You only get 2018, because you are trying to close a connection not opened correctly. Your only error code seems to be 2059, wich suggests the QM isn’t actually running when “migrated”. Have you checked the QM error logs?
– Attila Repasi
Jan 2 at 17:06
MQ versions below for your reference:- $dspmqver -a Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Linux (x86-64 platform) Mode: 64-bit O/S: Linux 2.6.32-754.6.3.el6.x86_64 InstName: Installation1 InstDesc: Primary: Yes InstPath: /opt/mqm DataPath: /var/mqm MaxCmdLevel: 802 -------------------------------------------------------- $rpm -qa | grep MQSeriesClient MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8009-8.0.0-9.x86_64
– Syed Mudhasir
Jan 3 at 11:08
Both of us asked for what the QM error logs have, can you provide?
– JoshMc
Jan 6 at 2:53
What does the error log on the queue manager show? What specific v8.0.0.x do they upgrade to? What specific version is your MQ client?
– JoshMc
Jan 2 at 14:44
What does the error log on the queue manager show? What specific v8.0.0.x do they upgrade to? What specific version is your MQ client?
– JoshMc
Jan 2 at 14:44
You only get 2018, because you are trying to close a connection not opened correctly. Your only error code seems to be 2059, wich suggests the QM isn’t actually running when “migrated”. Have you checked the QM error logs?
– Attila Repasi
Jan 2 at 17:06
You only get 2018, because you are trying to close a connection not opened correctly. Your only error code seems to be 2059, wich suggests the QM isn’t actually running when “migrated”. Have you checked the QM error logs?
– Attila Repasi
Jan 2 at 17:06
MQ versions below for your reference:- $dspmqver -a Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Linux (x86-64 platform) Mode: 64-bit O/S: Linux 2.6.32-754.6.3.el6.x86_64 InstName: Installation1 InstDesc: Primary: Yes InstPath: /opt/mqm DataPath: /var/mqm MaxCmdLevel: 802 -------------------------------------------------------- $rpm -qa | grep MQSeriesClient MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8009-8.0.0-9.x86_64
– Syed Mudhasir
Jan 3 at 11:08
MQ versions below for your reference:- $dspmqver -a Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Linux (x86-64 platform) Mode: 64-bit O/S: Linux 2.6.32-754.6.3.el6.x86_64 InstName: Installation1 InstDesc: Primary: Yes InstPath: /opt/mqm DataPath: /var/mqm MaxCmdLevel: 802 -------------------------------------------------------- $rpm -qa | grep MQSeriesClient MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8009-8.0.0-9.x86_64
– Syed Mudhasir
Jan 3 at 11:08
Both of us asked for what the QM error logs have, can you provide?
– JoshMc
Jan 6 at 2:53
Both of us asked for what the QM error logs have, can you provide?
– JoshMc
Jan 6 at 2:53
add a comment |
1 Answer
1
active
oldest
votes
0
Check that your software is compatible with MQ 8.0.
I had a similar issue. It turned out that we needed to upgrade to Java 8.
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
add a comment |
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
});
}
});
draft saved
draft discarded
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%2f54006379%2fibm-mq-upgrade-causing-error-2059-and-error-2018%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Check that your software is compatible with MQ 8.0.
I had a similar issue. It turned out that we needed to upgrade to Java 8.
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
add a comment |
0
Check that your software is compatible with MQ 8.0.
I had a similar issue. It turned out that we needed to upgrade to Java 8.
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
add a comment |
0
0
0
Check that your software is compatible with MQ 8.0.
I had a similar issue. It turned out that we needed to upgrade to Java 8.
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
Check that your software is compatible with MQ 8.0.
I had a similar issue. It turned out that we needed to upgrade to Java 8.
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
answered Jan 3 at 0:47
Kevin ForsterKevin Forster
11
11
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
add a comment |
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
I checked in IBM website, for MQ 8 Java 7 seems to be compatible. Are you saying this is causing the issue? Any error log which I can check to confirm ? Currently this is the version :- java version "1.7.0_191" OpenJDK Runtime Environment (rhel-2.6.15.4.el6_10-x86_64 u191-b01) OpenJDK 64-Bit Server VM (build 24.191-b01, mixed mode)
– Syed Mudhasir
Jan 3 at 11:11
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f54006379%2fibm-mq-upgrade-causing-error-2059-and-error-2018%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
What does the error log on the queue manager show? What specific v8.0.0.x do they upgrade to? What specific version is your MQ client?
– JoshMc
Jan 2 at 14:44
You only get 2018, because you are trying to close a connection not opened correctly. Your only error code seems to be 2059, wich suggests the QM isn’t actually running when “migrated”. Have you checked the QM error logs?
– Attila Repasi
Jan 2 at 17:06
MQ versions below for your reference:- $dspmqver -a Name: WebSphere MQ Version: 8.0.0.9 Level: p800-009-180321.1 BuildType: IKAP - (Production) Platform: WebSphere MQ for Linux (x86-64 platform) Mode: 64-bit O/S: Linux 2.6.32-754.6.3.el6.x86_64 InstName: Installation1 InstDesc: Primary: Yes InstPath: /opt/mqm DataPath: /var/mqm MaxCmdLevel: 802 -------------------------------------------------------- $rpm -qa | grep MQSeriesClient MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8009-8.0.0-9.x86_64
– Syed Mudhasir
Jan 3 at 11:08
Both of us asked for what the QM error logs have, can you provide?
– JoshMc
Jan 6 at 2:53