Can HTTP binding cause to crash MQTT binding?

Add-ons Bindings
1

If i have unstable internet connection can HTTP binding cause to crash MQTT binding?

Fatal transport error: java.util.concurrent.TimeoutException

Here is errors after that mqtt stops working:

2017-03-13 01:48:54.322 [ERROR] [org.openhab.io.net.http.HttpUtil    ] - Fatal transport error: java.net.NoRouteToHostException: No route to host
2017-03-13 01:48:54.353 [ERROR] [ab.binding.http.internal.HttpBinding] - No response received from 'http://192.168.1.12/simread?clear=1'
...
2017-03-13 01:50:42.037 [INFO ] [eclipse.smarthome.model.script.Meteo] - Send
**2017-03-13 01:50:49.302 [ERROR] [.smarthome.model.script.actions.HTTP] - Fatal transport error: java.util.concurrent.TimeoutException**
2017-03-13 01:50:49.328 [INFO ] [eclipse.smarthome.model.script.Meteo] - Wunderground.com - null
...
2017-03-13 01:52:59.505 [ERROR] [org.openhab.io.net.http.HttpUtil    ] - Fatal transport error: java.net.NoRouteToHostException: No route to host
2017-03-13 01:52:59.519 [ERROR] [ab.binding.http.internal.HttpBinding] - No response received from 'http://192.168.1.12/simread?clear=1'

2017-03-13 01:57:06.224 [ERROR] [org.openhab.io.net.http.HttpUtil    ] - Fatal transport error: java.net.NoRouteToHostException: No route to host
2017-03-13 01:57:06.248 [ERROR] [ab.binding.http.internal.HttpBinding] - No response received from 'http://192.168.1.12/simread?clear=1'
2017-03-13 01:57:10.167 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
2017-03-13 01:57:10.208 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
2017-03-13 01:57:10.233 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
2017-03-13 01:57:10.251 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
2017-03-13 01:57:10.274 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
2017-03-13 01:57:10.309 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
2017-03-13 01:57:10.332 [ERROR] [n.mqtt.internal.MqttMessagePublisher] - Error publishing message: Too many publishes in progress
...
2017-03-13 02:08:56.966 [ERROR] [t.mqtt.internal.MqttBrokerConnection] - MQTT connection to broker was lost
Unexpected error (6)
	at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:115)[214:org.openhab.io.transport.mqtt:1.10.0.201702140757]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_101]
2017-03-13 02:08:56.971 [ERROR] [t.mqtt.internal.MqttBrokerConnection] - MQTT connection to 'oh2agdisk' was lost: Unexpected error : ReasonCode 6 : Cause : Unknown
2017-03-13 02:08:56.973 [INFO ] [t.mqtt.internal.MqttBrokerConnection] - Starting connection helper to periodically try restore connection to broker 'oh2agdisk'
2

That seems unlikely. As far as I know they operate completely independently of one another.

When you see these MQTT connection errors have you looked at your Broker’s logs to see if the Broker went down at this time?

Can you correspond any other errors or weird behavior during these times? There might be something else going on that is impacting your whole network at these times, not just access to the Internet.