- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: How Pathwork handle delay message
Operating System - OpenVMS
1752666
Members
5670
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-03-2006 12:20 AM
тАО07-03-2006 12:20 AM
Hi
I'm using PathWork v 7.1 on Windows XP. I have some questions about how Pathwork will handle out of sequence messages. For example if the receiver (Pathwork) expects messages come in sequence 1 , 2 and 3. However,if a receiver got 2,3 and 1.
I found that PathWork will wait for 1 to come ( wait 3 seconds ). It didnt pass 2 and 3 to upper layer until 1 comes.
I'm wondering whether this is a behavior of Pathwork or not. If this is a correct behavior then would it be possible to reduce a wait time ( 3 secs ).
Thanks in advance.
Regards
Seng
I'm using PathWork v 7.1 on Windows XP. I have some questions about how Pathwork will handle out of sequence messages. For example if the receiver (Pathwork) expects messages come in sequence 1 , 2 and 3. However,if a receiver got 2,3 and 1.
I found that PathWork will wait for 1 to come ( wait 3 seconds ). It didnt pass 2 and 3 to upper layer until 1 comes.
I'm wondering whether this is a behavior of Pathwork or not. If this is a correct behavior then would it be possible to reduce a wait time ( 3 secs ).
Thanks in advance.
Regards
Seng
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-03-2006 01:02 AM
тАО07-03-2006 01:02 AM
Solution
If it is using decnet :
The effect of delay factor is to increase the
retransmission time by increasing the average round trip delay time, thus allowing for additional network delay.
The value of the weighting factor is given by the delay weight characteristic.
Basically, delay weight determines how quickly the retransmission timer responds to variations in actual round-trip delay times. A low value of delay weight means that the retransmission timer responds quickly to each sample of round-trip delay time; a delay weight of 0 means that an estimate is nearly the same as the last actual sample of round trip delay. A high value for delay weight reduces the impact of recent variations in network delay; the higher the value, the closer each estimate of round trip delay is to the average of all estimates.
If it is using IP :
Retransmission occcurs after 1 sec (tcp_rexmit_interval_min) and the delay is doubled after each retransmission. It may also decide itself to retransmit e.g. when it receives duplicate acks.
Wim
The effect of delay factor is to increase the
retransmission time by increasing the average round trip delay time, thus allowing for additional network delay.
The value of the weighting factor is given by the delay weight characteristic.
Basically, delay weight determines how quickly the retransmission timer responds to variations in actual round-trip delay times. A low value of delay weight means that the retransmission timer responds quickly to each sample of round-trip delay time; a delay weight of 0 means that an estimate is nearly the same as the last actual sample of round trip delay. A high value for delay weight reduces the impact of recent variations in network delay; the higher the value, the closer each estimate of round trip delay is to the average of all estimates.
If it is using IP :
Retransmission occcurs after 1 sec (tcp_rexmit_interval_min) and the delay is doubled after each retransmission. It may also decide itself to retransmit e.g. when it receives duplicate acks.
Wim
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-03-2006 02:17 PM
тАО07-03-2006 02:17 PM
Re: How Pathwork handle delay message
Thanks very much Wim. I'm using Decnet so I assumed that this waiting behavior is the nature of Pathwork or Decnet for being relaiable.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP