JMX Monitoring Support For Local Process On Windows

If you are monitoring a local jvm process using jconsole or jvisualvm and aren’t able to view the Threads tab on jvisualvm or connect to jconsole, this post should provide some troubleshooting information.

Any application that is started on the Java SE 6 platform will support the Attach API, and so will automatically be made available for local monitoring and management when needed. This out of box jmx support doesn’t work on Windows though. On Windows platforms, for security reasons, local monitoring and management is only supported if your default temporary directory is on a file system that allows the setting of permissions on files and directories (for example, on a New Technology File System (NTFS) file system). It is not supported on a File Allocation Table (FAT) file system, which provides insufficient access controls.

The simplest solution to this problem is to execute your java process with this vm parameter
“-Dcom.sun.management.jmxremote”.

In case you have an NTFS file system and are still facing this problem, here is an step by step guide to establish ownership (I have not tried it though :)).

Reference – Monitoring and Management Using JMX Technology

Advertisement