high ingest throughput cause wowza port filtered autumatically

Hi, i am using Wowza Streaming Engine 4.7.8, ingest rtmp streaming than clients play on rtmp/hls/webrtc, it works fine when ingest throughput is under 90 Mb/s, but when it goes above 100 Mb/s, wowza port (443/1935/8087) will be blocked automatically, do i need to setup something to ingest high throughput ??

OS: CentOS Linux release 7.5.1804 (Core) (default install)
Firewalld: disabled
SElinux: disabled
iptables: no rules
CPU: Intel® Xeon® E-2174G CPU @ 3.80GHz
RAM: 64GB

on problem happened, port became filered

Thank you for submitting a support ticket @cliff eup. It looks like you are meeting the transcoder requirements. I’ll be sure to follow the conversation here at Wowza. Your ticket should be getting assigned today to an engineer.

The Transcoder feature in Wowza Streaming Engine 4.7.8 requires GNU C Library (glibc) 2.17 or later. CentOS 6 doesn’t support this minimum version of glibc. We recommend updating to CentOS 7 or using a different operating system if your workflow requires the Transcoder feature.

Thank you for the quick reply. As mention, this problem may relate to OS, glibc and java, here is the information.

CentOS: 7.5.1804

glibc: version 2.17 3

Java: i didn’t install java, wowza runs on its own java