3party/libzmq
0
0
Fork 0
mirror of https://github.com/zeromq/libzmq.git synced 2024-12-26 06:41:03 +08:00
Code Issues Projects Releases Wiki Activity
libzmq/tests/test_reconnect_ivl.cpp

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

85 lines
2.0 KiB
C++
Raw Permalink Normal View History

Relicense from LGPL3 + exceptions to Mozilla Public License version 2.0 Relicense permission collected from all relevant authors as tallied at: https://github.com/rlenferink/libzmq-relicense/blob/master/checklist.md The relicense grants are collected under RELICENSE/ and will be moved to the above repository in a later commit. Fixes https://github.com/zeromq/libzmq/issues/2376
2023-06-05 00:16:05 +01:00
/* SPDX-License-Identifier: MPL-2.0 */
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
#include "testutil.hpp"
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
#include "testutil_unity.hpp"
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: default test setUp/tearDown functions duplicated in many test programs Solution: define setUp/tearDown functions via SETUP_TEARDOWN_TESTCONTEXT macro where possible
2019-03-24 12:51:28 -04:00
SETUP_TEARDOWN_TESTCONTEXT
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
void test_reconnect_ivl_against_pair_socket (const char *my_endpoint_,
void *sb_)
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
{
void *sc = test_context_socket (ZMQ_PAIR);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
int interval = -1;
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
TEST_ASSERT_SUCCESS_ERRNO (
zmq_setsockopt (sc, ZMQ_RECONNECT_IVL, &interval, sizeof (int)));
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
TEST_ASSERT_SUCCESS_ERRNO (zmq_connect (sc, my_endpoint_));
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
bounce (sb_, sc);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
TEST_ASSERT_SUCCESS_ERRNO (zmq_unbind (sb_, my_endpoint_));
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
expect_bounce_fail (sb_, sc);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
TEST_ASSERT_SUCCESS_ERRNO (zmq_bind (sb_, my_endpoint_));
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
expect_bounce_fail (sb_, sc);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
TEST_ASSERT_SUCCESS_ERRNO (zmq_connect (sc, my_endpoint_));
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests do not follow naming style Solution: apply naming style
2018-05-27 07:01:36 -04:00
bounce (sb_, sc);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
test_context_socket_close (sc);
}
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: ipc transport not supported under Windows Solution: implement support
2019-10-19 14:46:53 +02:00
#if defined(ZMQ_HAVE_IPC) && !defined(ZMQ_HAVE_GNU)
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
void test_reconnect_ivl_ipc (void)
{
Problem: tests use hard-coded fixed IPC file path Solution: use wildcards or random directories to avoid races when multiple users are running the same test on the same machine
2019-01-13 14:50:07 +00:00
char my_endpoint[256];
Problem: close always fails with wildcard bind, since directory is not empty Solution: unlink the socket file first
2019-02-04 05:33:28 -05:00
make_random_ipc_endpoint (my_endpoint);
Problem: tests use hard-coded fixed IPC file path Solution: use wildcards or random directories to avoid races when multiple users are running the same test on the same machine
2019-01-13 14:50:07 +00:00
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
void *sb = test_context_socket (ZMQ_PAIR);
Problem: close always fails with wildcard bind, since directory is not empty Solution: unlink the socket file first
2019-02-04 05:33:28 -05:00
TEST_ASSERT_SUCCESS_ERRNO (zmq_bind (sb, my_endpoint));
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: tests use hard-coded fixed IPC file path Solution: use wildcards or random directories to avoid races when multiple users are running the same test on the same machine
2019-01-13 14:50:07 +00:00
test_reconnect_ivl_against_pair_socket (my_endpoint, sb);
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
test_context_socket_close (sb);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
}
#endif
Problem: code from bind_loopback_ipv4 is duplicated Solution: call bind_loopback_ipv4 where applicable
2019-03-24 13:17:22 -04:00
void test_reconnect_ivl_tcp (bind_function_t bind_function_)
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
{
char my_endpoint[MAX_SOCKET_STRING];
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
void *sb = test_context_socket (ZMQ_PAIR);
Problem: code from bind_loopback_ipv4 is duplicated Solution: call bind_loopback_ipv4 where applicable
2019-03-24 13:17:22 -04:00
bind_function_ (sb, my_endpoint, sizeof my_endpoint);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
test_reconnect_ivl_against_pair_socket (my_endpoint, sb);
test_context_socket_close (sb);
}
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
void test_reconnect_ivl_tcp_ipv4 ()
{
Problem: code from bind_loopback_ipv4 is duplicated Solution: call bind_loopback_ipv4 where applicable
2019-03-24 13:17:22 -04:00
test_reconnect_ivl_tcp (bind_loopback_ipv4);
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
}
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
void test_reconnect_ivl_tcp_ipv6 ()
{
if (is_ipv6_available ()) {
zmq_ctx_set (get_test_context (), ZMQ_IPV6, 1);
Problem: code from bind_loopback_ipv4 is duplicated Solution: call bind_loopback_ipv4 where applicable
2019-03-24 13:17:22 -04:00
test_reconnect_ivl_tcp (bind_loopback_ipv6);
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
}
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
}
int main (void)
{
setup_test_environment ();
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
UNITY_BEGIN ();
Problem: mingw build broken Solution: check correct preprocessor define in test_reconnect_ivl to match the test invocation
2019-12-28 19:23:18 +01:00
#if defined(ZMQ_HAVE_IPC) && !defined(ZMQ_HAVE_GNU)
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
RUN_TEST (test_reconnect_ivl_ipc);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
#endif
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
RUN_TEST (test_reconnect_ivl_tcp_ipv4);
RUN_TEST (test_reconnect_ivl_tcp_ipv6);
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
Problem: test_reconnect_ivl not using unity Solution: migrate to unity, and reduce code duplication
2018-03-15 11:47:57 +01:00
return UNITY_END ();
Problem: zmq_connect fails after disconnect due to RECONNECT_IVL == -1 Solution: when a connection breaks and ZMQ_RECONNECT_IVL is set to -1, which means a reconnection will not be attempted, send a message from the I/O thread to the application thread to make the socket call term_endpoint, which is the equivalent of manually calling zmq_disconnect. This way subsequent zmq_connect call to the same endpoint will attempt again to do a connection. Otherwise, for some socket types like SUBs, those new connects will fail as the endpoint is recorded, despite the connection having been permanently closed. Add test cases to exercise this corner case with TCP and IPC.
2017-09-19 00:14:10 +01:00
}
Reference in New Issue Copy Permalink