Can’t collect Check Point FW Logs, via TCP over TLS

Elastic Stack Logstash
3

Hello,

Thank you for your answer.
I tried with the delimiter but it doesn't work either.
Here's the new configuration :

input {
  tcp {
    port => 55555
    mode => "server"
    codec => line {
      delimiter => "\n"
    }
    ssl_enabled => true
    ssl_certificate => "/path/to/logstash.crt"
    ssl_key => "/path/to/logstash.key"
    ssl_certificate_authorities => ["/path/to/ca.crt"]
    ssl_client_authentication => "none"
    ssl_supported_protocols => "TLSv1.2"
  }
}
output{
  stdout {
    codec => rubydebug
  }
}

For UDP, I have only the port in my configuration and it works fine :

input {
  udp {
    port => 55550
  }
}
output{
  stdout {
    codec => rubydebug
  }
}

I don't understand why there are different behaviours with the same TCP configuration, depending on where the data come from.
It seems that only with Check Point Firewall logs (TCP over TLS), Logstash acts like a buffer until I stop it.

Is there something I do wrong or did I forget something in my configurations ?
I didn't do anything more than what I sent previously.