-
Notifications
You must be signed in to change notification settings - Fork 472
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
ZMQ Heartbeat causes disconnect from server #193
Comments
Interesting, we added heartbeat and latest fixes from zmq repo to solve
this type of problem and firewall disconnect issues.
Cisco users reported back that old issues solved by latest heartbeat fix.
Did you check with latest image? Could you provide more information?
Thanks,
Hanoh
On Fri, 15 Feb 2019 at 11:15 jtraue ***@***.***> wrote:
Hi,
my client application disconnected randomly from the server due to a
timeout while waiting for the server to reply to a message. I was able to
trace the problem down to zeromq's heartbeats. If zmq transmits a heartbeat
while I want to send a message, my message is dropped. Naturally, the
server does not reply to messages which never came in , resulting in a
timeout.
My observations adhere to a bug reported in zmq: zeromq/libzmq#3060
<zeromq/libzmq#3060> As of version 4.3.0 is
should be fixed.
When I disable the heartbeats, everything seems to be fine. Unfortunately,
I did not have time to try zeromq's version 4.3.0.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#193>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMbjvV91HBwMIjGmwd7WL-yvWFPh6z-gks5vNnq9gaJpZM4a9PYQ>
.
--
Hanoh
Sent from my iPhone
|
It seems we don’t have the fix for this issue
https://github.com/cisco-system-traffic-generator/trex-core/blob/master/external_libs/zmq-x86_64/how_to_build.txt
Thanks for reporting
Thanks,
Hanoh
On Fri, 15 Feb 2019 at 11:15 jtraue ***@***.***> wrote:
Hi,
my client application disconnected randomly from the server due to a
timeout while waiting for the server to reply to a message. I was able to
trace the problem down to zeromq's heartbeats. If zmq transmits a heartbeat
while I want to send a message, my message is dropped. Naturally, the
server does not reply to messages which never came in , resulting in a
timeout.
My observations adhere to a bug reported in zmq: zeromq/libzmq#3060
<zeromq/libzmq#3060> As of version 4.3.0 is
should be fixed.
When I disable the heartbeats, everything seems to be fine. Unfortunately,
I did not have time to try zeromq's version 4.3.0.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#193>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMbjvV91HBwMIjGmwd7WL-yvWFPh6z-gks5vNnq9gaJpZM4a9PYQ>
.
--
Hanoh
Sent from my iPhone
|
Can you verify with latest master code with v4.3.1 ZMQ lib? |
I can not reproduce the error using master and 4.3.1 anymore. |
Thanks again for your finding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
my client application disconnected randomly from the server due to a timeout while waiting for the server to reply to a message. I was able to trace the problem down to zeromq's heartbeats. If zmq transmits a heartbeat while I want to send a message, my message is dropped. Naturally, the server does not reply to messages which never came in , resulting in a timeout.
My observations adhere to a bug reported in zmq: zeromq/libzmq#3060 As of version 4.3.0 is should be fixed.
When I disable the heartbeats, everything seems to be fine. Unfortunately, I did not have time to try zeromq's version 4.3.0.
The text was updated successfully, but these errors were encountered: