[syslog-ng] tcp on syslog 2.0.x vs 3.3.x

Best, Is it possible there is a different behaviour in the tcp destination. We see a different behaviour. We had a working setup with 2.0.x and while upgrading to 3.3.x we noticed the newlines in our messages are seen as EOM, causing a part of our logging to be lost. Is there a quick workaround for this? Kind regards Hannes De Bondt