到目前为止，这是我所做的：
1. I have deployed a java 11 application on aws fargate and it is up and running.
2. Task definition is correctly configured for tcp port mapping to application port
and jmx port (3939).
3. There is VPC configuration which allows communication between my network and aws.
4. Application is started with these additional system properties for
remote jmx connections:
-Dcom.sun.management.jmxremote.port=3939
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
5. From my local machine I am successfully able to telnet to private IP of fargate task
and jmx port 3939.
但是，当我尝试使用JVisualVm或JDK任务控件连接到jmx时，它无法连接。我在这里想念什么吗？
在我添加了以下提到的属性后，它终于起作用了，该属性强制rmi端口与jmx端口相同，而不是打开未从安全组打开的随机端口。
-Dcom.sun.management.jmxremote.rmi.port=3939
由于这些stackoverflow帖子：
本文收集自互联网，转载请注明来源。
如有侵权，请联系[email protected] 删除。
我来说两句