HiveMQ

Unknown TCP-Ports

Moin,

I just checked the TCP-Ports my HiveMQ process is using. So I found thees 3:

root@boulder ~ # ps -eaf | grep hivemq
hivemq 2358 1 0 Mar05 ? 00:47:04 java -Dhivemq.home=/opt/hivemq -Djava.net.preferIPv4Stack=true -noverify --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED --add-exports java.base/jdk.internal.misc=ALL-UNNAMED -Djava.security.egd=file:/dev/./urandom -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9010 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -XX:+CrashOnOutOfMemoryError -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/hivemq/heap-dump.hprof -jar /opt/hivemq/bin/hivemq.jar

root@boulder ~ # netstat -tulpen | grep 2358
tcp 0 0 0.0.0.0:9010 0.0.0.0:* LISTEN 1238 31902850 2358/java
tcp 0 0 0.0.0.0:8883 0.0.0.0:* LISTEN 1238 31902903 2358/java
tcp 0 0 0.0.0.0:39987 0.0.0.0:* LISTEN 1238 31902849 2358/java

8883: Okay, the TLS secured mqtt port
9010: Do I need this jmxremote port spreading to the world?
39987: What is it good for?

Grateful for any advice

Micha

Just for the record: Solved the problem by disabling jmx in the run.sh. So the jmx port is gone as well as the high (random) port.

2 Likes