Recently, I’ve started to receive warnings from the Ambient Weather binding that a connection was leaked. I’m not exactly sure when this started, but it’s fairly recent. Probably since migrating to 4.1.0. As far as I know nothing changed on my end, so I’m not sure why I’m getting this. Is anybody else getting these warnings? I have no issue changing the log level to suppress these, but I’d hate to do that when the binding is reporting a real issue.
Marty
2024-02-22 08:42:35.014 [WARN ] [okhttp3.OkHttpClient ] - A connection to https://api.ambientweather.net/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
2024-02-22 08:47:35.015 [WARN ] [okhttp3.OkHttpClient ] - A connection to https://api.ambientweather.net/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
2024-02-22 08:47:35.015 [WARN ] [okhttp3.OkHttpClient ] - A connection to https://api.ambientweather.net/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);