With Netty's PR 11732, Netty projects stops to re-package jars in netty-all dependency, so all the Netty deps used by the project has to be explicited listed, and this started with version 4.1.69.
With version 4.1.78 was shipped the PR 12438 which in SslContext needs the unix socket domains, packaged in netty-transport-native-unix-common.
Why is it important/What is the impact to the user?
Keeps the dependencies updated.
Checklist
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have made corresponding change to the default configuration files (and/or docker env variables)
[ ] I have added tests that prove my fix is effective or that my feature works
Author's Checklist
[x] run locally
In Gemfile
gem "logstash-input-tcp", :path => "/path/to/logstash-input-tcp"
bin/logstash-plugin install --no-verify
Release notes
Update Netty to
4.1.87What does this PR do?
With Netty's PR 11732, Netty projects stops to re-package jars in
netty-alldependency, so all the Netty deps used by the project has to be explicited listed, and this started with version4.1.69. With version4.1.78was shipped the PR 12438 which inSslContextneeds the unix socket domains, packaged innetty-transport-native-unix-common.Why is it important/What is the impact to the user?
Keeps the dependencies updated.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
bin/logstash -e "input{tcp{port => 1234 codec => json}} output {stdout {codec => rubydebug}}"
echo "{\"name\": \"John\"}" | nc localhost 1234
Related issues