You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are trying to build netty-tcnative 1.1.33 on s390x platform.
We built netty-tcnative 1.1.33 on s390x using OpenJDK-1.8 to get boringssl-static jar.
We were able to build after few changes as given https://github.com/linux-on-ibm-z/docs/wiki/Building-netty-tcnative (Unknown processor, and Unknown target CPU).
Though boring-ssl Jar bundled with logstash:5.5.1, but communication is not getting established between Filebeat and Logstash. Filebeat is throwing tls:ServerkeyExchange Error
In the mean while we came to know that netty uses BoringSSL which does not support Big Endian where as s390x is a Big Endian architecture. BoringSSL requires the architecture be little-endian. The compilation is not an issue but we do not get the desired results.
Is there any other library we can use to overcome the TLS issue?
Can you please suggest how to go further on this ?
The text was updated successfully, but these errors were encountered:
We are trying to build netty-tcnative 1.1.33 on s390x platform.
We built netty-tcnative 1.1.33 on s390x using OpenJDK-1.8 to get boringssl-static jar.
We were able to build after few changes as given
https://github.com/linux-on-ibm-z/docs/wiki/Building-netty-tcnative (Unknown processor, and Unknown target CPU).
Though boring-ssl Jar bundled with logstash:5.5.1, but communication is not getting established between Filebeat and Logstash. Filebeat is throwing
tls:ServerkeyExchange Error
In the mean while we came to know that netty uses BoringSSL which does not support Big Endian where as s390x is a Big Endian architecture. BoringSSL requires the architecture be little-endian. The compilation is not an issue but we do not get the desired results.
Is there any other library we can use to overcome the TLS issue?
Can you please suggest how to go further on this ?
The text was updated successfully, but these errors were encountered: