What steps will reproduce the problem?
1. Create a service that starts a mongoose server
2. Leave it working
3. After some time it stops responding requests
What is the expected output? What do you see instead?
I expected it to work without interruption
What version of the product are you using? On what operating system?
Trunk
Please provide any additional information below.
It seems that on android the network layer change a bit frequently, wifi goes
on/off phone radio goes on/off and with those changes the listening sockets get
invalidated, there is system messages that can be used to be notified but it
seems that the event loop of mongoose doesn't stop when the mainlistening
sockets get invalidated and it appears to be working when in reality it isn't.
There is some signals that are ignored on mg_start function.
Maybe we need to attach to another signal to catch when the main sockets get
invalidated to restart then.
Can someone give any clue with this issue ?
Original issue reported on code.google.com by
mingo...@gmail.comon 28 May 2012 at 7:26