You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is a better support channel, please let me know.
My application is running on Windows Server 2016. The latest windows updates and drivers are installed. I have run system file checker and it reports no issues.
My application occasionally crashes when attempting to read from the socket. The specific message is:
when calling int zmq_msg_recv(zmq_msg_t *msg_, void *s_, int flags_)
_flags_ is zmq::recv_flags::none.
Call stack:
Last source code in the call stack I have (I highlighted the offending line with >>>):
voidlisten()
{
while (true)
{
if (!zSocket)
{
return;
}
try
{
chat_message_t message;
>>> if (!zSocket->recv(message.type, zmq::recv_flags::none))
{
send_queue();
continue;
}
int more = zSocket->get(zmq::sockopt::rcvmore);
if (more)
{
std::ignore = zSocket->recv(message.data);
more = zSocket->get(zmq::sockopt::rcvmore);
if (more)
{
std::ignore = zSocket->recv(message.packet);
}
}
parse(message);
}
catch (zmq::error_t& e)
{
// Context was terminated (ETERM = 156384765)// Exit loopif (!zSocket || e.num() == 156384765)
{
return;
}
ShowError("Message: %s\n", e.what());
continue;
}
}
}
I'm not sure what steps I can take to tackle this problem. Our server has 20-70 simultaneous users (only three sessions are permitted from the same IP address). ZMQ doesn't really provide any method for tracking IP address on individual sockets, and it crashes while reading from the socket so I can't check what about the message might have caused it to crash. I'm not sure what other methods I can take to track/log this issue and attempt to develop a pattern.
We get this crash on average 1-2 times a day. We were affected by this exact same crash about four months ago, but it seemed to resolve itself for about 3 months before it cropped up again earlier this month. It is highly intermittent, but frequent enough to be severely disruptive. Server chugs along quite happily for ~12 hours and then crashes (despite the code being inside a try/catch block).
Note that I cannot do much to control the client our users use to connect to our server.
The text was updated successfully, but these errors were encountered:
Are you sure there are no concurrent uses for the zSocket? You could try adding a catch all block (catch(...)) to see if there are other types being thrown.
It looks like this comes from within libzmq so maybe you can try posting there if this does not help.
I am currently using CPPZMQ version 4.8.1.
If there is a better support channel, please let me know.
My application is running on Windows Server 2016. The latest windows updates and drivers are installed. I have run system file checker and it reports no issues.
My application occasionally crashes when attempting to read from the socket. The specific message is:
![image](https://private-user-images.githubusercontent.com/45589381/255426958-2daa5b1d-9068-49a7-854b-7f8cc3c9c289.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwMTA3NTcsIm5iZiI6MTcyNDAxMDQ1NywicGF0aCI6Ii80NTU4OTM4MS8yNTU0MjY5NTgtMmRhYTViMWQtOTA2OC00OWE3LTg1NGItN2Y4Y2MzYzljMjg5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDE5NDczN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRkMzZlYWMwY2YyNDk0Mzk4YjNiZWE4YjhiYzgwZGY0NGQxMjZhZDY0MzUxOGFiMGM4ZDFjOTA5MjdiZWY5NTgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0._01yRDTU5SxTRnFhKpipHSV0SCogttuLa2SYgqVpgnw)
when calling
int zmq_msg_recv(zmq_msg_t *msg_, void *s_, int flags_)
_flags_
iszmq::recv_flags::none
.Call stack:
![image](https://private-user-images.githubusercontent.com/45589381/255427085-4d91ba66-bf25-43d5-9883-252134cbf547.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwMTA3NTcsIm5iZiI6MTcyNDAxMDQ1NywicGF0aCI6Ii80NTU4OTM4MS8yNTU0MjcwODUtNGQ5MWJhNjYtYmYyNS00M2Q1LTk4ODMtMjUyMTM0Y2JmNTQ3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDE5NDczN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ5MWY1YjhiYzc3YWEyMWUxMjExNDU0YzY0MDliNWE5OWIzZGUwZDFkMTBkZjc4MjYyNjRlMTNlN2UwM2ZiYjgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.93HNsxYM3nbXG67ZCq9RMa03byRvIrdz4jZ6MgaNHB4)
Last source code in the call stack I have (I highlighted the offending line with
>>>
):I'm not sure what steps I can take to tackle this problem. Our server has 20-70 simultaneous users (only three sessions are permitted from the same IP address). ZMQ doesn't really provide any method for tracking IP address on individual sockets, and it crashes while reading from the socket so I can't check what about the message might have caused it to crash. I'm not sure what other methods I can take to track/log this issue and attempt to develop a pattern.
We get this crash on average 1-2 times a day. We were affected by this exact same crash about four months ago, but it seemed to resolve itself for about 3 months before it cropped up again earlier this month. It is highly intermittent, but frequent enough to be severely disruptive. Server chugs along quite happily for ~12 hours and then crashes (despite the code being inside a
try/catch
block).Note that I cannot do much to control the client our users use to connect to our server.
The text was updated successfully, but these errors were encountered: