-
Notifications
You must be signed in to change notification settings - Fork 0
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
Avoid startup freezes of OMJulia #9
Comments
The restart solution seems to work. I just got the following warnings:
But no OMC instance was left open after the simulations finished. |
Second time that i encountered a frozen connection with the new solution, still no dangling OMC instance. This seems to work reliably. 👍 |
Another interesting observation: It seems possible that the first warning is shown without the second warning, meaning that it is not unreasonable to hope, that closing the OMC will work smoothly. Also: Third occurrence of warning, still no dangling OMC processes. 🎉 |
New case report: Two warnings, one dangling OMC instance. This means that the warning message is also justified.
[cslz90@cswork ~]$ ps -aux | grep omc
cslz90 6987 0.0 0.2 1287812 42072 pts/0 Sl+ 11:35 0:00 omc --interactive=zmq +z=julia.xyzKRHj35I
cslz90 8727 0.0 0.0 6672 2468 pts/2 S+ 11:39 0:00 grep --colour=auto omc |
Sometimes, OMJulia freezes when the first command is sent to the OMC, indefinitely waiting for an answer.
My current solution for this was to attempt to implement a timeout for
ZMQ.recv
, however this currently yields the following error:I guess when ZMQ freezes during
revc
, it cannot change its state variables, which lead to a subsequent send operation triggering this StateError. A solution might be to simply restart the whole connection when this occurs.The text was updated successfully, but these errors were encountered: