-
Notifications
You must be signed in to change notification settings - Fork 176
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
server stop responding after some time #595
Comments
I get the same issue randomly in our production app. I've added logging around the |
I am not sure if I am doing it the wrong way or not but when I dispose the server there is no log |
@RagibNoor our production app is a Xamarin forms app with a web view front end. Still haven't figured out the root cause but done quite a bit to just make sure not hammering EmbedIO. Added a queue and command store on front-end that basically queues requests to EmbedIO so we don't send multiple requests at same time. But some things we still don't and generally it's around there where we get error. The latest change is detecting when getting no response from EmbedIO from front-end and send a message through the web view to restart EmbedIo. Still getting embed io killing itself heaps in production so now doing a proof of concept REST-like API that goes directly through web view instead. |
for me with xamarin it's working fine |
Describe the bug
After upgrading from Xamarin to MAUI, I encountered an issue with EmbedIO. Within my application, I run two EmbedIO servers: one serves the frontend static files and the other handles backend APIs. However, after a certain number of calls from the frontend application, the backend server stops responding. This issue only seems to occur in device builds.
To Reproduce
Steps to reproduce the behavior:
1 Upgrade from Xamarin to MAUI.
2 Set up two EmbedIO servers within the application.
3 Make several calls from the frontend application to the backend server.
4 Observe that after a certain number of calls, the backend server stops responding.
Expected behavior
The backend server should continue to respond to requests from the frontend application without interruption, regardless of the number of calls made.
The text was updated successfully, but these errors were encountered: