Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to reconnect when Receiver fails? #21

Open
baek-eng opened this issue Feb 28, 2022 · 2 comments
Open

How to reconnect when Receiver fails? #21

baek-eng opened this issue Feb 28, 2022 · 2 comments

Comments

@baek-eng
Copy link

I am seeing the following error message:

Error: [OSCReceiver] Receive error: System.Net.Sockets.SocketException (0x80004005): The socket is not connected
at System.Net.Sockets.SocketAsyncResult.CheckIfThrowDelayedException () [0x00000] in <00000000000000000000000000000000>:0
at System.Net.Sockets.Socket.EndReceiveFrom (System.IAsyncResult asyncResult, System.Net.EndPoint& endPoint) [0x00000] in <00000000000000000000000000000000>:0
at System.Net.Sockets.UdpClient.EndReceive (System.IAsyncResult asyncResult, System.Net.IPEndPoint& remoteEP) [0x00000] in <00000000000000000000000000000000>:0
at extOSC.Core.Network.OSCReceiverStandaloneBackend.Receive (System.Net.Sockets.UdpClient receivedClient, System.IAsyncResult result) [0x00000] in <00000000000000000000000000000000>:0
at extOSC.Core.Network.OSCReceiverStandaloneBackend.ControllerThread (System.IAsyncResult result) [0x00000] in <00000000000000000000000000000000>:0
at System.AsyncCallback.Invoke (System.IAsyncResult ar) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.WaitCallback.Invoke (System.Object state) [0x00000] in <00000000000000000000000000000000>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <00000000000000000000000000000000>:0

I am seeing that we're swallowing the exception here:

Debug.LogError($"[OSCReceiver] Receive error: {e}");

Is there a way to reconnect on receive failure? (or does it reconnect automatically?)

@Iam1337
Copy link
Owner

Iam1337 commented Mar 2, 2022

Interesting, this is the first time I've seen this error. After it, most likely you need to reconnect. What are you sending and receiving to get this error?

@baek-eng
Copy link
Author

baek-eng commented Mar 2, 2022

We're just sending an array of floats (about 50-60 or so).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants