-
Notifications
You must be signed in to change notification settings - Fork 35
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
Error when interface is not working #6
Comments
I will take a look at that. Are you using a WiFi access point and moving out of range or using an ad hoc WiFi net?
…Sent from my iPhone
On Feb 17, 2020, at 7:51 AM, Michael Möbius ***@***.***> wrote:
When I use NORM over WiFi and the connection goes down(not disabling the interface) I see the following error in the log, but I don't get any event to handle the issue:
2020-01-29 12:58:01.749 ? W/protolib: NormSession::SendMessage() sendto(224.1.2.3/4102) warning: Invalid argument
2020-01-29 12:58:01.752 ? E/protolib: ProtoSocket::SendTo() sendto() error: Invalid argument
The error is shown in an endless loop and I can't handle it. Is there any way to determine if NORM can send the data correctly?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I am using an WiFi access point. And I am just powering off the access point for this test. |
I am on travel this week so it will be a few days before I can set up a similar test. If you could set the NORM debug level and logging to capture some debug output, I could possibly see what type of error message (likely a socket error message) is produced for that condition and determine the best strategy for handling it. Most of our own testing over Wifi has been in ad hoc mode.
So, it sound like you would benefit from getting a notification when your access point connect is lost? At the moment, NORM keeps trying to send packets hoping that any sendto() error will go away … it is possible that a NORM API notification could be issued when that occurs … The key is being able to discern between an error that is a single occurrence vs. a more significant event.
… On Feb 18, 2020, at 12:41 AM, Michael Möbius ***@***.***> wrote:
I am using an WiFi access point. And I am just powering off the access point for this test.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=ABU46GNOCIUJRP6JASQM2H3RDNYKJA5CNFSM4KWQ7D62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMAU62A#issuecomment-587288424>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABU46GNFYEFX6EHUAMHKCK3RDNYKJANCNFSM4KWQ7D6Q>.
|
I am using the Loglevel 7, //PL_MAX, and I don't get any more info from NORM.
But NORM is not showing anything. Norm is printing these stats sometime after the disconnect:
And a short time after that, it runns into the endless loop of:
Yes exactly I would benefit from a notification that the data can't be send so I can handle it in my app. Otherwise I have no idea if the data was send or not. |
A couple of more questions:
(Also sorry I haven't been able to address this yet. I need to set up something so I can test this but have not been able to be in my office much. I have Android devices and an access point I can use to replicate your situation ... it's the time that's hard to find). |
I just pushed updated code that extends the NORM_SEND_ERROR notification posting cases to cover the sort of error you are getting. I have not tested it for your specific issue and did not change the "polling" behavior with regards to send retry attempts ... but with the notification you can now decide what to do at the app layer |
Thank you! |
Sorry for the delay. Now I found the time to test your new version. Thank you for the improvement! |
When I use NORM on Android over an WiFi and the connection goes down(not disabling the interface) I see the following error in the log, but I don't get any event to handle the issue:
The error is shown in an endless loop and I can't handle it. Is there any way to determine if NORM can send the data correctly?
The text was updated successfully, but these errors were encountered: