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
* @throws \RuntimeException if listening on this address fails (already in use etc.)
I am uncertain if a workaround is available for this as I haven't dove deeper into this repository, however I have a niche use-case where I have a game server running in another process which outputs http requests as webhooks to my instance of SocketServer. If the SocketServer goes offline at any point the game server which is making the calls to the SocketServer does not stop listening on whatever port the SocketServer was previously listening on, so if the SocketServer tries to restart it will fail to do so as it will be unable to rebind to the port.
This issue could be avoided when using a traditional Socket by simply utilizing the SO_REUSEPORT constant with socket_get_option, but so far I have not seen a way to do this with react/socket.
The text was updated successfully, but these errors were encountered:
valzargaming
changed the title
SocketServer throws RuntimeException if already listening on this address fails
SocketServer throws RuntimeException if already listening on this port
May 9, 2025
socket/src/SocketServer.php
Line 32 in 78ebd28
I am uncertain if a workaround is available for this as I haven't dove deeper into this repository, however I have a niche use-case where I have a game server running in another process which outputs http requests as webhooks to my instance of SocketServer. If the SocketServer goes offline at any point the game server which is making the calls to the SocketServer does not stop listening on whatever port the SocketServer was previously listening on, so if the SocketServer tries to restart it will fail to do so as it will be unable to rebind to the port.
This issue could be avoided when using a traditional Socket by simply utilizing the SO_REUSEPORT constant with socket_get_option, but so far I have not seen a way to do this with react/socket.
The text was updated successfully, but these errors were encountered: