-
Notifications
You must be signed in to change notification settings - Fork 485
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
Jeromq protocol not supported exception on windows build #997
Comments
Can you try it without jython ? |
I cannot. I have created a python version of ZeroMQ on the same computer. This works fine but I need to have it working on Jython. Thank you |
I don’t understand. Is the error comming from jython ? JeroMQ ? JeroMQ called from jython Does it works with earlier versions ? |
I am unsure if it is a jython thing or jeromq. I have not tried earlier versions. Do you suggest earlier versions of jeromq or to try another Java based system? I also would like to know what the error corresponds to. Thank you |
“Anthony Java based system“ ? What are you talking about ? |
Sorry typo , Athony= another. To be honest I would like to know what "error 43 protocol not supported" means. I am unsure if I compiled it wrong and missing libraries, or jython and jeromq are not compatible. I will try earlier versions of jeromq. I did try to look up earlier versions that maybe compatible with my jython version. I was not able to correlate it. |
Without a simple reproductible case, we cannot help you. |
@Kwasi-v I agree. I suspect it related to jython. Protocol not supported means the connection protocl isn't supported. For example, "tcp://localhost:12345" would use TCP. What is your connection string? For both the bind and connect? |
Hi,
I built jeromq 0.6.0 on windows 11. Everytime I try to create a basic TCP socket connection I am getting error 43: protocol not supported. I am trying to use JeroMQ on Jython 2.7.3. Any help or ideas for things to check would be appreciated.
Follow up:
Same error on all other protocols I try to use for connection.
Changing the socket type does not work either.
The text was updated successfully, but these errors were encountered: