Also hier tauchen seit dem Update auch vermehrt folgende Fehler im Log auf:
Code:
29.12.2013 - 21:13:48.369 ERROR WetterInput - Fehler beim Abruf der Warntypen
java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.dwd.de/bvbw/appmanager/bvbw/dwdwwwDesktop?_nfpb=true&_windowLabel=T14600649251144330032285&_urlType=action&_pageLabel=_dwdwww_wetter_warnungen_warnungen&WEEKLY_REPORT_VIEW=false&TIME=x&SHOW_HEIGHT_SEL=true&MAP_VIEW=false&MOVIE_VIEW=false&TABLE_VIEW=true&HEIGHT=x&SHOW_TIME_SEL=true&STATIC_CONTENT_VIEW=false&WARNING_TYPE=0&LAND_CODE=EM
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) ~[na:1.7.0_21]
	at java.net.URL.openStream(Unknown Source) ~[na:1.7.0_21]
	at wetterwarnerInput.WetterInput.updateTypesOfWarnings(WetterInput.java:244) [WeatherwarnerInput.jar:na]
	at wetterwarnerInput.WetterInput.updateWeatherSituation(WetterInput.java:371) [WeatherwarnerInput.jar:na]
	at wetterwarnerInput.WetterInput$WetterTimer.run(WetterInput.java:610) [WeatherwarnerInput.jar:na]
	at java.util.TimerThread.mainLoop(Unknown Source) [na:1.7.0_21]
	at java.util.TimerThread.run(Unknown Source) [na:1.7.0_21]
W3.org sagt zwar zu HTTP 503:
Code:
10.5.4 503 Service Unavailable

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

      Note: The existence of the 503 status code does not imply that a
      server must use it when becoming overloaded. Some servers may wish
      to simply refuse the connection.
Komisch finde ich es aber schon, da mir die fehler vorher nicht aufgefallen sind.
Vielleicht kann man ja mal testweise einbauen, dass er bei einem Response Code 503 innerhalb einer Minute nochmal versucht, die Daten abzurufen.