-
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
periodic index-out-of-bounds error #938
Comments
@stealthrabbi Can you verify if this is still an issue with v0.5.3? |
@trevorbernard I will try. The issue is that the exception sometimes takes many days to surface -- it's hard to pin down. Do you happen to have a list of things changed in 0.5.2 -> 0.5.3 |
No the issue still exists in 0.5.3. Took about 24 hours to recreate. In my program, I've added an exception handler for this case, but I see now that the exception continues forever. I am guessing I need to create a new zmq socket. I also don't know if I can reuse the ZContext I created when my program starts, or if a new ZContext is needed. |
Just to be sure, the XPub socket is not shared between threads ? |
Can you try with this branch: https://github.com/fbacchella/jeromq/tree/issue938 ? |
I am still seeing this issue with version 0.5.4. |
This branch was not merged as nobody provided any feebdback. |
I added the changes to the Dist.java in my local 0.5.4 environment and recompiled/installed the change. While I'm not getting the stack trace, it appears that my app is silently failing now. I'm going to dig into this more. |
I'm also experiencing this issue and for me it seems fairly easily reproduceable:
In my setup, a Java application creates a zeromq socket of tpye SocketType.PUB and connects to a XPUB/XPUB router. The connection is setup in the constructor of a class, and the oob exception is triggered periodically (but i can see it happening at least once a day in my current setup). |
Using v0.5.2
My program is able to run days sending binary pictures, but will occasionally encounter an IndexOutOfBoundsException. I am not sure if it's an apparent issue with the data being sent to the zmq client, or something with a connection. The issue is not easily repeatable.
Also, are there release notes for different versions? I see there's now a 0.5.3, but I can't tell what's been added to it.
The text was updated successfully, but these errors were encountered: