После того, как потоки MongoSocketReadTimeoutException @Scheduled были разрушены ⇐ JAVA

[Anonymous]

Из журналов видно, что каждое запланированное задание занимает свой собственный поток. Я установил размер пула на 10 из них, и он работал нормально до исключения MongoDB. Поскольку у нас есть три кластера, у всех истекло время ожидания, и после этого поток монитора успешно подключился к серверу с описанием (ко всем трем кластерам)
INFO 6 --- [ scheduling-1]
INFO 6 --- [ scheduling-1]
INFO 6 --- [ scheduling-6]
INFO 6 --- [ scheduling-6]
INFO 6 --- [ scheduling-6]
INFO 6 --- [ scheduling-6]
INFO 6 --- [ scheduling-8]
INFO 6 --- [ scheduling-8]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-7]
INFO 6 --- [ scheduling-7]
INFO 6 --- [ scheduling-8]
INFO 6 --- [ scheduling-8]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-3]
INFO 6 --- [ scheduling-3]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-10]
INFO 6 --- [ scheduling-6]
INFO 6 --- [ scheduling-6]
INFO 6 --- [ scheduling-5]
INFO 6 --- [ scheduling-5]
INFO 6 --- [ scheduling-2]
INFO 6 --- [ scheduling-2]
INFO 6 --- [ scheduling-2]
INFO 6 --- [ scheduling-2]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-7]
INFO 6 --- [ scheduling-7]
INFO 6 --- [ scheduling-8]
INFO 6 --- [ scheduling-8]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [XXX] org.mongodb.driver.cluster : Exception in monitor thread while connecting to server XXX

После этого логи такие. С этого момента все задания начинали выполняться в одном и том же потоке один или несколько раз, а затем потоки менялись таким образом. Также полностью перестало выполняться одно из запланированных заданий.
INFO 6 --- [XXX] org.mongodb.driver.cluster : Monitor thread successfully connected to server with description ServerDescription
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-9]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-4]
INFO 6 --- [ scheduling-4]


Подробнее здесь: https://stackoverflow.com/questions/791 ... got-ruined