{"action":"created","issue":{"url":"https://api.github.com/repos/logstash/logstash-logback-encoder/issues/87","labels_url":"https://api.github.com/repos/logstash/logstash-logback-encoder/issues/87/labels{/name}","comments_url":"https://api.github.com/repos/logstash/logstash-logback-encoder/issues/87/comments","events_url":"https://api.github.com/repos/logstash/logstash-logback-encoder/issues/87/events","html_url":"https://github.com/logstash/logstash-logback-encoder/issues/87","id":60308218,"number":87,"title":"v4.2 with SSL is not pushing events continously","user":{"login":"pricefx","id":7803108,"avatar_url":"https://avatars.githubusercontent.com/u/7803108?v=3","gravatar_id":"","url":"https://api.github.com/users/pricefx","html_url":"https://github.com/pricefx","followers_url":"https://api.github.com/users/pricefx/followers","following_url":"https://api.github.com/users/pricefx/following{/other_user}","gists_url":"https://api.github.com/users/pricefx/gists{/gist_id}","starred_url":"https://api.github.com/users/pricefx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pricefx/subscriptions","organizations_url":"https://api.github.com/users/pricefx/orgs","repos_url":"https://api.github.com/users/pricefx/repos","events_url":"https://api.github.com/users/pricefx/events{/privacy}","received_events_url":"https://api.github.com/users/pricefx/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2015-03-09T07:38:02Z","updated_at":"2015-03-13T07:27:14Z","closed_at":null,"body":"Hi, \r\nwe're trying to send our log events via an encrypted channel. The setup per se seems allright as events come accross occasionally, but not as real-time as with plain TCP.\r\nSo the behaviour after a while is this:\r\nYou generate log events. Nothing appears in ES (or also in the receiving logstash stdout). When we bounce the receiving logstash service, most of the time a whole bunch of old messages comes in. So the broken connection fixes it temporarily, but obviously this isn't a permanent solution.\r\n\r\nThe setup:\r\n\r\n  \t<appender name=\"LOGSTASH_ERROR\" class=\"net.logstash.logback.appender.LogstashTcpSocketAppender\">\r\n\t    <filter class=\"ch.qos.logback.classic.filter.ThresholdFilter\">\r\n\t        <level>ERROR</level>\r\n\t    </filter>  \t\r\n    \t<remoteHost>${logstash-server}</remoteHost>\r\n      \t<port>5000</port>\r\n      \t<encoder class=\"net.logstash.logback.encoder.LogstashEncoder\">\r\n\t\t\t<Pattern>\r\n\t\t\t\t%d{HH:mm:ss.SSS} %X{cluster} %X{req.requestURI} %X{batchsize} %X{username} - %msg%n\r\n\t\t\t</Pattern>\r\n\t\t</encoder>\r\n\t\t<!-- Enable SSL using the JVM's default keystore/truststore -->\r\n\t\t<ssl>\r\n\t\t    <trustStore>\r\n\t\t        <location>classpath:pricefx-logstash.jks</location>\r\n\t\t        <password>pricefx</password>\r\n\t\t    </trustStore>\r\n\t\t</ssl>\t\r\n  \t</appender> \r\n\r\nThe receiving end:\r\n\r\n\r\n    input {\r\n      tcp {\r\n    port => 5000\r\n    codec => json\r\n    type => \"logs\"\r\n    ssl_cert => \"/etc/logstash/tls/logstash.crt\"\r\n    ssl_key => \"/etc/logstash/tls/logstash.key\"\r\n    ssl_enable => true\r\n    data_timeout => 300\r\n      }\r\n    }\r\n\r\nI played already with a few config options, but due to the lack of a clear error message I am a bit stuck. Happy to provide logs or debug dumps or so if needed.\r\n\r\nCheers\r\nChris"},"comment":{"url":"https://api.github.com/repos/logstash/logstash-logback-encoder/issues/comments/78847237","html_url":"https://github.com/logstash/logstash-logback-encoder/issues/87#issuecomment-78847237","issue_url":"https://api.github.com/repos/logstash/logstash-logback-encoder/issues/87","id":78847237,"user":{"login":"pricefx","id":7803108,"avatar_url":"https://avatars.githubusercontent.com/u/7803108?v=3","gravatar_id":"","url":"https://api.github.com/users/pricefx","html_url":"https://github.com/pricefx","followers_url":"https://api.github.com/users/pricefx/followers","following_url":"https://api.github.com/users/pricefx/following{/other_user}","gists_url":"https://api.github.com/users/pricefx/gists{/gist_id}","starred_url":"https://api.github.com/users/pricefx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pricefx/subscriptions","organizations_url":"https://api.github.com/users/pricefx/orgs","repos_url":"https://api.github.com/users/pricefx/repos","events_url":"https://api.github.com/users/pricefx/events{/privacy}","received_events_url":"https://api.github.com/users/pricefx/received_events","type":"User","site_admin":false},"created_at":"2015-03-13T07:27:14Z","updated_at":"2015-03-13T07:27:14Z","body":"I don't think I have the same issue. I do not see parsing errors at the receiving end and the behaviour is also appearing with an openssl server at the backend"}}