{"action":"closed","issue":{"url":"https://api.github.com/repos/spring-projects/spring-integration-kafka/issues/32","labels_url":"https://api.github.com/repos/spring-projects/spring-integration-kafka/issues/32/labels{/name}","comments_url":"https://api.github.com/repos/spring-projects/spring-integration-kafka/issues/32/comments","events_url":"https://api.github.com/repos/spring-projects/spring-integration-kafka/issues/32/events","html_url":"https://github.com/spring-projects/spring-integration-kafka/issues/32","id":69627332,"number":32,"title":"Pull out network cable - no way to recover","user":{"login":"erolosty","id":436451,"avatar_url":"https://avatars.githubusercontent.com/u/436451?v=3","gravatar_id":"","url":"https://api.github.com/users/erolosty","html_url":"https://github.com/erolosty","followers_url":"https://api.github.com/users/erolosty/followers","following_url":"https://api.github.com/users/erolosty/following{/other_user}","gists_url":"https://api.github.com/users/erolosty/gists{/gist_id}","starred_url":"https://api.github.com/users/erolosty/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/erolosty/subscriptions","organizations_url":"https://api.github.com/users/erolosty/orgs","repos_url":"https://api.github.com/users/erolosty/repos","events_url":"https://api.github.com/users/erolosty/events{/privacy}","received_events_url":"https://api.github.com/users/erolosty/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-04-20T16:37:06Z","updated_at":"2015-05-31T12:39:32Z","closed_at":"2015-05-31T12:39:32Z","body":"We want to be able to reconnect automatically if a network connection is dropped. When we use the Consumer it seems to spin up runnables into threads, but unfortunately in exceptional circumstances (such as disabling the network connection) - the ListenerContainer is left in a state were isRunning=true but the threads have bombed out, and .start() would need to be called to resume Consumption of messages - but with no way for client code to know that the ListenerContainer is no longer working, knowing that we should call start() is impossible"}}