Author |
Message
|
Thiru |
Posted: Mon Jan 09, 2023 5:20 am Post subject: |
|
|
Novice
Joined: 22 Dec 2022 Posts: 21
|
Hughson Worte
Quote: |
Hi Thiru,
Is it possible that your listener hasn't started properly as part of the failover?
You say that when you have this problem, you are still able to use runmqsc. Can you use DISPLAY LSTATUS(*) to check that your listener is running next time this happens? |
Thiru: The listener will start automatically with failover all the time and we can see the status as well.
I am still having the problem and just now ran the below command.
DISPLAY LSSTATUS(*)
and I got the result listener status details as running.
Thanks !
Thiru |
|
Back to top |
|
 |
Thiru |
Posted: Mon Jan 09, 2023 5:31 am Post subject: |
|
|
Novice
Joined: 22 Dec 2022 Posts: 21
|
Bruce2359 Wrote:
Quote: |
I've seen this behavior occasionally. Try this:
- stop the MQExplorer
Restart the MQExplorer with options to clear Eclipse cache
- strmqcfg -c
or
- strmqcfg -i
Please tell us the results. |
Thiru: Can you advise how exactly you want me to stop the mq explorer? As i mentioned earlier my queue managers are running on windows system.
Thanks !
Thiru. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Jan 09, 2023 7:49 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Thiru wrote: |
Bruce2359 Wrote:
Quote: |
I've seen this behavior occasionally. Try this:
- stop the MQExplorer
Restart the MQExplorer with options to clear Eclipse cache
- strmqcfg -c
or
- strmqcfg -i
Please tell us the results. |
Thiru: Can you advise how exactly you want me to stop the mq explorer? As i mentioned earlier my queue managers are running on windows system.
Thanks !
Thiru. |
To stop a Windows app, in this case, the MQExplorer:
- Right-Click the X at the top RIGHT of the MQExplorer window banner, OR
- click Fiie->Exit, OR
- kill the process via the Windows Process Explorer app or similar. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
hughson |
Posted: Mon Jan 09, 2023 12:54 pm Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
Thiru wrote: |
Hughson Worte
Quote: |
Hi Thiru,
Is it possible that your listener hasn't started properly as part of the failover?
You say that when you have this problem, you are still able to use runmqsc. Can you use DISPLAY LSTATUS(*) to check that your listener is running next time this happens? |
Thiru: The listener will start automatically with failover all the time and we can see the status as well.
I am still having the problem and just now ran the below command.
DISPLAY LSSTATUS(*)
and I got the result listener status details as running.
Thanks !
Thiru |
And yet you get MQRC_HOST_NOT_AVAILABLE when you try to connect a client MQ Explorer? Can you ping the same address you are using in the client MQ Explorer from the machine where the client MQ Explorer is running?
Cheers,
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
Thiru |
Posted: Mon Jan 09, 2023 9:59 pm Post subject: |
|
|
Novice
Joined: 22 Dec 2022 Posts: 21
|
Bruce2359 Wrote
To stop a Windows app, in this case, the MQExplorer:
- Right-Click the X at the top RIGHT of the MQExplorer window banner, OR
- click Fiie->Exit, OR
- kill the process via the Windows Process Explorer app or similar.
Thriu : Tried with same but no luck ! |
|
Back to top |
|
 |
Thiru |
Posted: Mon Jan 09, 2023 10:03 pm Post subject: |
|
|
Novice
Joined: 22 Dec 2022 Posts: 21
|
Hughson Wrote:
And yet you get MQRC_HOST_NOT_AVAILABLE when you try to connect a client MQ Explorer? Can you ping the same address you are using in the client MQ Explorer from the machine where the client MQ Explorer is running?
Thiru: I am able to ping the IP address from the remote machine without any issue and sender/receiver connection to both servers also works every day.
even the client connections (Servconn's also running fine) only issue with MQ Explore |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Jan 10, 2023 7:50 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
I'd strongly suggest that you open a PMR with IBM on this issue.
One more thing to try, start MQExplorer with the debug -x switch:
strmqcfg -x
-x switch will write debug messages to the console
Post results here.
Another thing:
Is the Command Server running on the qmgr(s)?
Is the SYSTEM.COMMAND.INPUT queue put/get enabled? Current depth? _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Thiru |
Posted: Thu Jan 12, 2023 4:51 am Post subject: |
|
|
Novice
Joined: 22 Dec 2022 Posts: 21
|
bruce2359 wrote: |
I'd strongly suggest that you open a PMR with IBM on this issue.
One more thing to try, start MQExplorer with the debug -x switch:
strmqcfg -x
-x switch will write debug messages to the console
Post results here.
Another thing:
Is the Command Server running on the qmgr(s)?
Is the SYSTEM.COMMAND.INPUT queue put/get enabled? Current depth? |
Thiru: Please find the results from strmqcfg -x below and I don't see any queue as SYSTEM.COMMAND.INPUT but I can see below queues and their depth's 0 PUT & GET also enabled.
1) SYSTEM.ADMIN. COMMAND.QUEUE
2) SYSTEM.ADMIN. COMMAND.EVENT
Quote: |
tart VM: -Xmx512M
-Djava.class.path=C:\MQM\bin64\\../mqexplorer/eclipse/plugins/org.eclipse.equi
nox.launcher_1.5.700.v20200207-2156.jar
-os win32
-ws win32
-arch x86_64
-showsplash
-launcher C:\MQM\bin64\MQExplorer.exe
-name MQExplorer
--launcher.library C:\MQM\bin64\\../mqexplorer/eclipse/plugins/org.eclipse.equ
inox.launcher.win32.win32.x86_64_1.1.1100.v20190907-0426\eclipse_1902.dll
-startup C:\MQM\bin64\\../mqexplorer/eclipse/plugins/org.eclipse.equinox.launc
her_1.5.700.v20200207-2156.jar
--launcher.overrideVmargs
-consolelog
-debug
-vm C:\MQM\bin64\\../java/jre/bin\j9vm\jvm.dll
-vmargs
-Xmx512M
-Djava.class.path=C:\MQM\bin64\\../mqexplorer/eclipse/plugins/org.eclipse.equi
nox.launcher_1.5.700.v20200207-2156.jar
Install location:
file:/c:/MQM/MQExplorer/eclipse/
Configuration file:
file:/c:/MQM/MQExplorer/eclipse/configuration/config.ini loaded
Configuration location:
file:/C:/Users/Thiru/.eclipse/com.ibm.mq.explorer.ui.rcp.RcpApplication_9
.2.2.202103051724_1923615891_win32_win32_x86_64/configuration/
Configuration file:
file:/C:/Users/Thiru/.eclipse/com.ibm.mq.explorer.ui.rcp.RcpApplication_9
.2.2.202103051724_1923615891_win32_win32_x86_64/configuration/config.ini loaded
Loading timestamp file from:
file:/C:/Users/Thiru/.eclipse/com.ibm.mq.explorer.ui.rcp.RcpApplicat
ion_9.2.2.202103051724_1923615891_win32_win32_x86_64/configuration/ .baseConfi
gIniTimestamp
Timestamps found:
config.ini in the base: 1647941868653
remembered 1647941868653
Shared configuration location:
file:/c:/MQM/MQExplorer/eclipse/configuration/
Framework located:
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi_3.15.200.v2020021
4-1600.jar
Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.1.700.v
20200207-2156.jar
eclipse.properties not found
Loading extension: reference:file:org.eclipse.osgi.compatibility.state.nl1_1.1.7
00.v202003051653.jar
eclipse.properties not found
Loading extension: reference:file:org.eclipse.osgi.compatibility.state.nl2_1.1.7
00.v202003051653.jar
eclipse.properties not found
Loading extension: reference:file:org.eclipse.osgi.nl1_3.15.200.v202003051653.ja
r
eclipse.properties not found
Loading extension: reference:file:org.eclipse.osgi.nl2_3.15.200.v202003051653.ja
r
eclipse.properties not found
Framework classpath:
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi_3.15.200.v2020021
4-1600.jar
file:/c:/MQM/MQExplorer/eclipse/plugins/
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi.compatibility.sta
te_1.1.700.v20200207-2156.jar
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi.compatibility.sta
te.nl1_1.1.700.v202003051653.jar
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi.compatibility.sta
te.nl2_1.1.700.v202003051653.jar
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi.nl1_3.15.200.v202
003051653.jar
file:/c:/MQM/MQExplorer/eclipse/plugins/org.eclipse.osgi.nl2_3.15.200.v202
003051653.jar
Splash location:
C:\Users\Thiru\.eclipse\com.ibm.mq.explorer.ui.rcp.RcpApplication_9.2.2.2
02103051724_1923615891_win32_win32_x86_64\configuration\org.eclipse.equinox.laun
cher\com.ibm.mq.explorer.branding_9.2.2.202103051724\splash.bmp
Debug options:
file:/C:/MQM/bin64/.options not found
Time to load bundles: 31
Starting application: 2187
MQ Explorer: Using existing workspace: /C:/Users/Thiru/IBM/WebSphereMQ/worksp
ace/ (MQ 9.2)
Application started in : 5625ms |
|
|
Back to top |
|
 |
bruce2359 |
Posted: Sat Jan 14, 2023 4:08 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
I asked you the status of the command server on the affected qmgrs.
Issue this command: DISPLAY QMSTATUS CMDSERV _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Jan 15, 2023 2:34 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
I have seen MQRC_HOST_NOT_AVAILABLE to be a product of poor authentication combination:
- user and password mismatch. Could be because user is too long (should not be over 12 chars)
- missing the USE MQCSP flag
Have you tried running amqscnxc from the Samples directory?
Have you checked the entry in the error logs of the qmgr?
Does the MQ Service user have authorization to read group membership and group membership SAM?
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Jan 16, 2023 10:33 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
I asked you the status of the command server on the affected qmgrs.
Please issue these commands, post results here:
DISPLAY QMSTATUS ALL
DISPLAY QSTATUS(SYSTEM.ADMIN.COMMAND.QUEUE) _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Jan 16, 2023 10:50 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
I simulated the symptoms you've described.
I launched the MQExplorer, created a new qmgr, successfully viewed local queues.
Next, I opened a command prompt with runmqsc, and put-inhibited the SYSTEM.ADMIN.COMMAND.QUEUE. The MQExplorer content panes disappeared.
Next, using the command prompt runmqsc, I put(enabled) the SYSTEM.ADMIN.COMMAND.QUEUE. Clicked the refresh icon on the MQExplorer, and the content panes re-appeared.
When next you experience the symptoms, use runmqsc to display put/get for the SYSTEM.ADMIN.COMMAND.QUEUE. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
hughson |
Posted: Mon Jan 16, 2023 2:14 pm Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
bruce2359 wrote: |
I simulated the symptoms you've described. |
Did you get the same error message about a pending connection? _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Jan 16, 2023 6:02 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
hughson wrote: |
bruce2359 wrote: |
I simulated the symptoms you've described. |
Did you get the same error message about a pending connection? |
Nope, I did not get the MQRC_HOST_NOT_AVAILABLE (2538) error. I tested on a plain Windows MQ v9.0 image, no MI or other failover capabilities, local qmgr, no SYSTEM.ADMIN.SVRCON channel.
PMR time.
I’d seen this loss-of-content-pane symptom, and discovered the cause to be the command queue put-inhibited. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Thiru |
Posted: Tue Jan 31, 2023 3:51 am Post subject: |
|
|
Novice
Joined: 22 Dec 2022 Posts: 21
|
Hi All,
Apologies for late reply, as I was on vacation.
The monthly failover was happened few days before and I can see the queue manager and its objects under MQ explorer.
I'll share the results in few days as it is happening very frequently. |
|
Back to top |
|
 |
|