In my running WowzaStreamingEngine, I’ve seen that WowzaStreamingEngine is listening in these TCP ports:
LISTEN 0 100 0.0.0.0:1935 0.0.0.0:* users:((“java”,pid=1709,fd=229))
LISTEN 0 100 0.0.0.0:8083 0.0.0.0:* users:((“java”,pid=1709,fd=234))
LISTEN 0 100 0.0.0.0:8086 0.0.0.0:* users:((“java”,pid=1709,fd=240))
LISTEN 0 100 0.0.0.0:8443 0.0.0.0:* users:((“java”,pid=1709,fd=237))
LISTEN 0 50 0.0.0.0:8087 0.0.0.0:* users:((“java”,pid=1709,fd=222))
LISTEN 0 50 0.0.0.0:34567 0.0.0.0:* users:((“java”,pid=1709,fd=8))
The last one (34567) is dynamic. It change in each service restart.
I can’t find documentation about it and I’m worried that someone may have installed malware in the Java product.
How can I know if that it’s ok to have the WowzaStreamingEngine also listening on that TCP port and what is that for? Where is it documented?
Hello,
it’s no malware but standard Java behavior.
This is a random port picked for the JMX interface.
Please see the jconsole with Wowza Streaming Engine documentation for details.
You can verify this by running
jconsole 127.0.0.1:34567
(using the currently active listening port) in a terminal, and jconsole will show you to which port it connected.
If you would want a fixed port for firewall or for monitoring, then you can uncomment and set both Dcom.sun.management.jmxremote.port and Dcom.sun.management.jmxremote.rmi.port in the startup script files wms.sh and startup.sh located at the bin directory.
You can disable JMX entirely if not needed or explicitly configure secure access using SSL settings in the config.
Also, ports should be blocked for external access if you don’t require this service and vice versa, if you require it, then it is important to assign it a port.
Regards,
Bernd Backhaus
Wowza Support
WOWZA | The solution you start with, the partner you scale with.
Wowza Video is here! Look at all the new features that will help elevate your business.
Manage your Support cases online
Bookmark our FAQ page
Bookmark our Status page