| Title: | NAS Message Queuing Bus |
| Notice: | KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10 |
| Moderator: | PAMSRC::MARCUS EN |
| Created: | Wed Feb 27 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2898 |
| Total number of notes: | 12363 |
My customer is experiencing network problems, and would like to
experiment with the dmqld ping interval and heartbeat variables to try
to cut the every-1.5-minute link loss he is seeing. I am not
recommending this approach to him, but I do have to be responsive to
his questions (BTW, this is not the same development team from 2436.*).
He is using v3.0B (I'm tremendously annoyed with them, their next
release is NOT going to v3.2A, they are waiting until the release after
that). He would like to know that, since the default timeout of 60 sec
is longer than the interval of 15 sec, whether when the ping goes out,
and the response is a long time coming, do the following pings wait for
the response, or just continue every 15 sec?
He also wants to know what happens if these parameters are set
differently on the remote group.
In the meantime, after re-reading 2436.*, I'm ready to fill him in on
the problems he will continue to encounter because his project manager
decided not to take any risks by switching to more recent middleware
(and hence DmQ) versions. At least the groups on the client side of
the equation are upgrading to v3.2A over the next two months.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2777.1 | XHOST::SJZ | Rocking the Messaging Desktop ! | Tue Feb 18 1997 22:21 | 7 | |
subsequent pings are sent no sooner than DMQLD_PING_INTERVAL
units of time AFTER receipt of a response. that is we do
not continue to send pings while there is one outstanding.
there is no need to.
_sjz.
| |||||
| 2777.2 | thanks | WHOS01::ELKIND | Steve Elkind, Digital SI @WHO | Tue Feb 18 1997 22:32 | 4 |
Thank you.
What is the effect of having different parameters on either end of the
link?
| |||||
| 2777.3 | XHOST::SJZ | Rocking the Messaging Desktop ! | Wed Feb 19 1997 00:09 | 7 | |
the link drivers ping each other independently of each other,
so the values need not be the same. however, if there is a
no response condition on the line, the one with the smaller
values should detect the condition sooner than the other.
_sjz.
| |||||
| 2777.4 | another question | WHOS01::ELKIND | Steve Elkind, Digital SI @WHO | Wed Feb 19 1997 22:17 | 4 |
Another question: say the packet with the ping request gets dropped by
a router under buffer-space-exhaustion conditions. If this were using
TCP, then it would be re-transmitted from the source. Will this happen
with the dmqld heartbeat, or is it sent using some form of UDP?
| |||||
| 2777.5 | XHOST::SJZ | Rocking the Messaging Desktop ! | Thu Feb 20 1997 09:10 | 3 | |
we use TCP not UDP.
_sjz.
| |||||