|LocalEventTimer||Singleton Timer subclass to run polling tasks that generate events for local Java Virtual Machines..||code | html|
|LocalMonitoredVm||Concrete implementation of the AbstractMonitoredVm class for the local: protocol for the HotSpot PerfData monitoring implementation.||code | html|
|LocalMonitoredVm.NotifierTask||Class to notify listeners of Monitor related events for the target JVM.||code | html|
|LocalVmManager||Class for managing the LocalMonitoredVm instances on the local system.||code | html|
|MonitoredHostProvider||Concrete implementation of the MonitoredHost interface for the local protocol of the HotSpot PerfData monitoring implementation.||code | html|
|MonitoredHostProvider.NotifierTask||Class to poll the local system and generate event notifications.||code | html|
|PerfDataBuffer||The concrete PerfDataBuffer implementation for the local: protocol for the HotSpot PerfData monitoring implementation.||code | html|
|PerfDataFile||Class to provide translations from the local Vm Identifier name space into the file system name space and vice-versa.||code | html|
Provides the implementation classes for the local: protocol for the HotSpot PerfData instrumentation buffer monitoring implementation.
The local: protocol is the default protocol for the PerfData implementation. It utilizes a name shared memory mechanism, identified by a backing store file in the file system name space. The location of the backing store file is platform specific and is dictated primarily by the JVM implementation. However, the java.io.tmpdir system property generally contains the location of the files, with the exception of the Solaris implementation, as the SDK and HotSpot JVM use different locations for their temporary file storage. The HotSpot JVM uses the /tmp directory and the SDK uses /var/tmp. The classes in this specifically use /tmp when running on Solaris.