Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repetitive packets with same messageId #169

Open
levshkatov opened this issue Mar 2, 2018 · 4 comments
Open

Repetitive packets with same messageId #169

levshkatov opened this issue Mar 2, 2018 · 4 comments
Labels

Comments

@levshkatov
Copy link

I make 5 simultaneous GET requests to 5 different hosts. The problem is that sometimes I receive same packets with same messageId. Did anybody face this problem?

@GiedriusM
Copy link
Collaborator

Hi @levshkatov ,

Could you elaborate more on how your setup is working? Maybe you're having packet loss and packets are retransmitted. Did you try capturing traffic on all 6 hosts?

@stale
Copy link

stale bot commented Jul 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 13, 2020
@stale
Copy link

stale bot commented Jul 21, 2020

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions.

@stale stale bot closed this as completed Jul 21, 2020
@jogry
Copy link

jogry commented Nov 22, 2023

in case of wakama code. messageId generated with a "rand()". and seed value set "srand(time(NULL)". as we know "time(NULL)" generate value in second.
if there are many client that connect to server at same time. they all use same seed value to generate messageId. so all of them have same messageId.
you have to use another unique seed value to generate messageId, not only time.

@JKRhb JKRhb reopened this Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants