All Versions

For all J2SE versions, you can use the -Xmanagement option autodiscovery to instruct JDP to announce the presence of a JRockit JVM instance; for example -Xmanagement:autodiscovery=true.

Table 4 lists additional system properties you can use to control the behavior of the JDP server:

System Properties Used to Control the JDP Server

System Property	Description	Default
jrockit.managementserver.discovery.period	The time to wait, in ms, between multicasting the presence	5000
jrockit.managementserver.discovery.ttl	The number of router hops the packets being multicasted should survive	1
jrockit.managementserver.discovery.address	The multicast group or address to use	232.192.1.212
jrockit.managementserver.discovery.targetport	The target port to broadcas	7090(1.4)/7091(1.5)

All versions of JRockit Mission Control also employ an additional protocol when using the Memory Leak Detector. The Memleak Server is an integral part of the JRockit JVM.

MLP (MemLeak Protocol) is used by the Memory Leak server during a memory leak detection session. JRockit Mission Control communicates over RMP (1.4) or JMXRMI (5.0 and later) to ask the JRockit JVM to start the server. You can configure the port on which you want to start the Memleak Server for this session by using JRockit Mission Control preferences.