We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I have hit the following issue:
If I set:
requester.setReqRelaxed(true); requester.setReqCorrelate(true);
on a REQ socket using tcp the socket no longer receives any data. The full example looks like this:
ZContext context = new ZContext(); var replier = context.createSocket(SocketType.REP); replier.bind("tcp://127.0.0.1:9877"); replier.setLinger(0); var requester = context.createSocket(SocketType.REQ); requester.connect("tcp://127.0.0.1:9877"); requester.setLinger(0); requester.setReqRelaxed(true); requester.setReqCorrelate(true); requester.send(new byte[] {(byte) 8, (byte) 2}); var request = replier.recv(); assertThat(request).isEqualTo(new byte[] {(byte) 8, (byte) 2}); replier.send(new byte[] {(byte) 8, (byte) 2}); var reply = requester.recv(); assertThat(reply).isEqualTo(new byte[] {(byte) 8, (byte) 2}); requester.close(); replier.close(); context.close();
If the setCorrelated and setRelaxed calls are removed, the example runs. Same holds true if I replace tcp by inproc.
I am using version 0.5.2 from maven central:
implementation group: 'org.zeromq', name: 'jeromq', version: '0.5.2'
There is a seemingly related issue, but it's not exactly the same: #442
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I have hit the following issue:
If I set:
on a REQ socket using tcp the socket no longer receives any data. The full example looks like this:
If the setCorrelated and setRelaxed calls are removed, the example runs. Same holds true if I replace tcp by inproc.
I am using version 0.5.2 from maven central:
There is a seemingly related issue, but it's not exactly the same: #442
The text was updated successfully, but these errors were encountered: