Author |
Message
|
tychak |
Posted: Sun Sep 26, 2004 10:09 pm Post subject: Channel status not updating |
|
|
Novice
Joined: 16 Mar 2004 Posts: 19
|
I have two QM on two hosts, named QMA on Host A and QMB on Host B.
There are both sender and receiver channel between two queue managers. The status of the channels is idle such that there is no message being tranmitted from QMA to QMB. When I stop the listener on host B, the status of the sender channel on QMA is still "running". If I manually stop and restart the channel, the channel status becomes "retrying". It is not desirable to tranmit test message.
Is there anyway to update the channel status without stop/restart the channel? Is there a fast way to force updateing the status of the channel? Is it useful to use the parameters such as HBINT?
Thanks. |
|
Back to top |
|
 |
siliconfish |
Posted: Sun Sep 26, 2004 10:59 pm Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
If you want to update the status, set the Heartbeat Interval and TCP/IP Keepalive. Heartbeat acts at MQ level and Keepalive acts at OS level(except Z/OS which can be set as a channel attribute). |
|
Back to top |
|
 |
PGoodhart |
Posted: Mon Sep 27, 2004 5:17 am Post subject: |
|
|
Master
Joined: 17 Jun 2004 Posts: 278 Location: Harrisburg PA
|
Is this being viewed through the MQ Explorer in windows by any chance? I have noticed that when you think you see an inconsistency it is caused by an out of sync display that needs to be refreshed (a fairly common windows programming issue). This doesn't seem to happen with runmqsc. With the Explore I just make sure I go up and hit the refresh button before I get excited about anything. (It has gotten to be second nature.) _________________ Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
Back to top |
|
 |
tychak |
Posted: Tue Sep 28, 2004 12:00 am Post subject: |
|
|
Novice
Joined: 16 Mar 2004 Posts: 19
|
I've changed HBINT and enabled TCP keepalive. The result shows the channel status of QMA's sender channel is updated faster when it goes from "RUNNING" to "RETRYING" when the QMB is down in Host A. However, when QMB is up again, the status of QMA's sender channel is keeping at "RETRYING" for a very long time. There is no message being transmitted and the channel is idel. Any way to make this faster?
I check the status with runmqsc and I believe there is no problem on the refresh screen on Window Explorer.
Thanks. |
|
Back to top |
|
 |
siliconfish |
Posted: Tue Sep 28, 2004 12:05 am Post subject: |
|
|
 Master
Joined: 12 Aug 2002 Posts: 203 Location: USA
|
Use ADOPTMCA on the receiving end. |
|
Back to top |
|
 |
|