You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but after test passes and redis is shutdown. Lettuce within rQueue is still trying to reconnect. It causes our test to hang for a while. Can you let me know how would we avoid that? We have lots of these logs:
{"@timestamp":"2022-02-16T16:55:37.599Z","@Version":"1","level":"INFO","message":"z Reconnecting, last destination was localhost/:6379"}
{"@timestamp":"2022-02-16T16:55:37.605Z","@Version":"1","level":"WARN","message":"z Cannot reconnect to [localhost/:6379]: Connection refused: localhost/127.0.0
Another question I have is: Do we need to start redis server, to be able to use rQueue? I would expect some sort of embedded redis would start within the library. But if I do not start redis explicitly I get redis connection errors.
The text was updated successfully, but these errors were encountered:
What's not working?
Hi, we start redis within our unit test framework as below:
@BeforeAll
static void setup() {
redisServer = RedisServer.builder().port(6379).build();
redisServer.start();
}
and we shutdown it like that:
but after test passes and redis is shutdown. Lettuce within rQueue is still trying to reconnect. It causes our test to hang for a while. Can you let me know how would we avoid that? We have lots of these logs:
{"@timestamp":"2022-02-16T16:55:37.599Z","@Version":"1","level":"INFO","message":"z Reconnecting, last destination was localhost/:6379"}
{"@timestamp":"2022-02-16T16:55:37.605Z","@Version":"1","level":"WARN","message":"z Cannot reconnect to [localhost/:6379]: Connection refused: localhost/127.0.0
Another question I have is: Do we need to start redis server, to be able to use rQueue? I would expect some sort of embedded redis would start within the library. But if I do not start redis explicitly I get redis connection errors.
The text was updated successfully, but these errors were encountered: