
Please report freshly implemented bugs here. I will try to fix those short term.
Moderator: Mattk
Requests to weather networks are not done in parallel as this will blow the RAM and performance limited SOCs of the Meteobridge. Therefore, requests are serialized and provided with a timeout, when no reply coming back in time. When CWOP internal IP resolution does point to nothing on their side, no error is returned, but Meteobridge waits until deciding to give up by its internal timeout definition. Now assume that some services are triggered every 10 seconds and the CWOP services again and again run into the 30 seconds timeout stall. Now requests will queue up and even when Meteobridge does try some smart priorization in the sending queue this will result into a mess after some time.