Will this cause the 2480 port to be inaccessible? Under what circumstances might this occur

[a-drop-of-tears]

0458-2062255.txt

[tglman]

Hi,

Thanks to report what version are you using ?

Regards

[a-drop-of-tears]

orientdb version:3.2.29 @tglman

[tglman]

Hi,

This seems a deadlock from the notification of database events and connection establish, I do remember similar problem in the past, that should have been fixed in the latest release, I will have a double check.

Regards

[tglman]

Hi,

this issue together with this: #10769 is a concurrency issue that should be already fixed in more recent releases than 3.2.29.

there are a few commits that change the push logic after 3.2.29, some re-write the concurrent push handling (and as far as I remember was because of these deadlock issues)

here a few of them:

0bc55b2a50 fix: make sure to terminate the push subscribe connection if fails to connect
dfad818135 fix: minor fix in push manager on concurrent subscribes and unsubscribes
c419d29965 fix: make sure to disconnect push session in case of push error, issue #10453

So to solve this problem the best way is to upgrade to a recent version.

[a-drop-of-tears]

Hello @tglman, thank you for providing detailed information