- current-thread-cpu-time-supported?
- dump-all-threads
- find-deadlocked-threads
- find-monitor-deadlocked-threads
- get-all-thread-ids
- get-current-thread-cpu-time
- get-current-thread-user-time
- get-daemon-thread-count
- get-peak-thread-count
- get-thread-count
- get-thread-cpu-time
- get-thread-info
- get-thread-user-time
- get-total-started-thread-count
- object-monitor-usage-supported?
- reset-peak-thread-count
- set-thread-contention-monitoring-enabled
- set-thread-cpu-time-enabled
- synchronizer-usage-supported?
- thread-contention-monitoring-enabled?
- thread-contention-monitoring-supported?
- thread-cpu-time-enabled?
- thread-cpu-time-supported?
jdk.lang.management.ThreadMXBean
The management interface for the thread system of the Java virtual machine.
A Java virtual machine has a single instance of the implementation class of this interface. This instance implementing this interface is an MXBean that can be obtained by calling the ManagementFactory.getThreadMXBean() method or from the platform MBeanServer method.
The ObjectName for uniquely identifying the MXBean for the thread system within an MBeanServer is:
java.lang:type=Threading
It can be obtained by calling the PlatformManagedObject.getObjectName() method.
Thread ID Thread ID is a positive long value returned by calling the Thread.getId() method for a thread. The thread ID is unique during its lifetime. When a thread is terminated, this thread ID may be reused.
Some methods in this interface take a thread ID or an array of thread IDs as the input parameter and return per-thread information.
Thread CPU time A Java virtual machine implementation may support measuring the CPU time for the current thread, for any thread, or for no threads.
The isThreadCpuTimeSupported() method can be used to determine if a Java virtual machine supports measuring of the CPU time for any thread. The isCurrentThreadCpuTimeSupported() method can be used to determine if a Java virtual machine supports measuring of the CPU time for the current thread. A Java virtual machine implementation that supports CPU time measurement for any thread will also support that for the current thread.
The CPU time provided by this interface has nanosecond precision but not necessarily nanosecond accuracy.
A Java virtual machine may disable CPU time measurement by default. The isThreadCpuTimeEnabled() and setThreadCpuTimeEnabled(boolean) methods can be used to test if CPU time measurement is enabled and to enable/disable this support respectively. Enabling thread CPU measurement could be expensive in some Java virtual machine implementations.
Thread Contention Monitoring Some Java virtual machines may support thread contention monitoring. When thread contention monitoring is enabled, the accumulated elapsed time that the thread has blocked for synchronization or waited for notification will be collected and returned in the ThreadInfo object.
The isThreadContentionMonitoringSupported() method can be used to determine if a Java virtual machine supports thread contention monitoring. The thread contention monitoring is disabled by default. The setThreadContentionMonitoringEnabled(boolean) method can be used to enable thread contention monitoring.
Synchronization Information and Deadlock Detection Some Java virtual machines may support monitoring of object monitor usage and ownable synchronizer usage. The getThreadInfo(long[], boolean, boolean) and dumpAllThreads(boolean, boolean) methods can be used to obtain the thread stack trace and synchronization information including which lock a thread is blocked to acquire or waiting on and which locks the thread currently owns.
The ThreadMXBean interface provides the findMonitorDeadlockedThreads() and findDeadlockedThreads() methods to find deadlocks in the running application.
The management interface for the thread system of the Java virtual machine. A Java virtual machine has a single instance of the implementation class of this interface. This instance implementing this interface is an MXBean that can be obtained by calling the ManagementFactory.getThreadMXBean() method or from the platform MBeanServer method. The ObjectName for uniquely identifying the MXBean for the thread system within an MBeanServer is: java.lang:type=Threading It can be obtained by calling the PlatformManagedObject.getObjectName() method. Thread ID Thread ID is a positive long value returned by calling the Thread.getId() method for a thread. The thread ID is unique during its lifetime. When a thread is terminated, this thread ID may be reused. Some methods in this interface take a thread ID or an array of thread IDs as the input parameter and return per-thread information. Thread CPU time A Java virtual machine implementation may support measuring the CPU time for the current thread, for any thread, or for no threads. The isThreadCpuTimeSupported() method can be used to determine if a Java virtual machine supports measuring of the CPU time for any thread. The isCurrentThreadCpuTimeSupported() method can be used to determine if a Java virtual machine supports measuring of the CPU time for the current thread. A Java virtual machine implementation that supports CPU time measurement for any thread will also support that for the current thread. The CPU time provided by this interface has nanosecond precision but not necessarily nanosecond accuracy. A Java virtual machine may disable CPU time measurement by default. The isThreadCpuTimeEnabled() and setThreadCpuTimeEnabled(boolean) methods can be used to test if CPU time measurement is enabled and to enable/disable this support respectively. Enabling thread CPU measurement could be expensive in some Java virtual machine implementations. Thread Contention Monitoring Some Java virtual machines may support thread contention monitoring. When thread contention monitoring is enabled, the accumulated elapsed time that the thread has blocked for synchronization or waited for notification will be collected and returned in the ThreadInfo object. The isThreadContentionMonitoringSupported() method can be used to determine if a Java virtual machine supports thread contention monitoring. The thread contention monitoring is disabled by default. The setThreadContentionMonitoringEnabled(boolean) method can be used to enable thread contention monitoring. Synchronization Information and Deadlock Detection Some Java virtual machines may support monitoring of object monitor usage and ownable synchronizer usage. The getThreadInfo(long[], boolean, boolean) and dumpAllThreads(boolean, boolean) methods can be used to obtain the thread stack trace and synchronization information including which lock a thread is blocked to acquire or waiting on and which locks the thread currently owns. The ThreadMXBean interface provides the findMonitorDeadlockedThreads() and findDeadlockedThreads() methods to find deadlocks in the running application.
current-thread-cpu-time-supported?clj
(current-thread-cpu-time-supported? this)Tests if the Java virtual machine supports CPU time measurement for the current thread. This method returns true if isThreadCpuTimeSupported() returns true.
returns: true
if the Java virtual machine supports CPU time
measurement for current thread;
false otherwise. - boolean
Tests if the Java virtual machine supports CPU time
measurement for the current thread.
This method returns true if isThreadCpuTimeSupported()
returns true.
returns: true
if the Java virtual machine supports CPU time
measurement for current thread;
false otherwise. - `boolean`dump-all-threadsclj
(dump-all-threads this locked-monitors locked-synchronizers)Returns the thread info for all live threads with stack trace and synchronization information. Some threads included in the returned array may have been terminated when this method returns.
This method returns an array of ThreadInfo objects as specified in the getThreadInfo(long[], boolean, boolean) method.
locked-monitors - if true, dump all locked monitors. - boolean
locked-synchronizers - if true, dump all locked ownable synchronizers. - boolean
returns: an array of ThreadInfo for all live threads. - java.lang.management.ThreadInfo[]
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").
Returns the thread info for all live threads with stack trace
and synchronization information.
Some threads included in the returned array
may have been terminated when this method returns.
This method returns an array of ThreadInfo objects
as specified in the getThreadInfo(long[], boolean, boolean)
method.
locked-monitors - if true, dump all locked monitors. - `boolean`
locked-synchronizers - if true, dump all locked ownable synchronizers. - `boolean`
returns: an array of ThreadInfo for all live threads. - `java.lang.management.ThreadInfo[]`
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").find-deadlocked-threadsclj
(find-deadlocked-threads this)Finds cycles of threads that are in deadlock waiting to acquire object monitors or ownable synchronizers.
Threads are deadlocked in a cycle waiting for a lock of these two types if each thread owns one lock while trying to acquire another lock already held by another thread in the cycle.
This method is designed for troubleshooting use, but not for synchronization control. It might be an expensive operation.
returns: an array of IDs of the threads that are
deadlocked waiting for object monitors or ownable synchronizers, if any;
null otherwise. - long[]
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").
Finds cycles of threads that are in deadlock waiting to acquire
object monitors or
ownable synchronizers.
Threads are deadlocked in a cycle waiting for a lock of
these two types if each thread owns one lock while
trying to acquire another lock already held
by another thread in the cycle.
This method is designed for troubleshooting use, but not for
synchronization control. It might be an expensive operation.
returns: an array of IDs of the threads that are
deadlocked waiting for object monitors or ownable synchronizers, if any;
null otherwise. - `long[]`
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").find-monitor-deadlocked-threadsclj
(find-monitor-deadlocked-threads this)Finds cycles of threads that are in deadlock waiting to acquire object monitors. That is, threads that are blocked waiting to enter a synchronization block or waiting to reenter a synchronization block after an Object.wait call, where each thread owns one monitor while trying to obtain another monitor already held by another thread in a cycle.
More formally, a thread is monitor deadlocked if it is part of a cycle in the relation "is waiting for an object monitor owned by". In the simplest case, thread A is blocked waiting for a monitor owned by thread B, and thread B is blocked waiting for a monitor owned by thread A.
This method is designed for troubleshooting use, but not for synchronization control. It might be an expensive operation.
This method finds deadlocks involving only object monitors. To find deadlocks involving both object monitors and ownable synchronizers, the findDeadlockedThreads method should be used.
returns: an array of IDs of the threads that are monitor
deadlocked, if any; null otherwise. - long[]
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").
Finds cycles of threads that are in deadlock waiting to acquire
object monitors. That is, threads that are blocked waiting to enter a
synchronization block or waiting to reenter a synchronization block
after an Object.wait call,
where each thread owns one monitor while
trying to obtain another monitor already held by another thread
in a cycle.
More formally, a thread is monitor deadlocked if it is
part of a cycle in the relation "is waiting for an object monitor
owned by". In the simplest case, thread A is blocked waiting
for a monitor owned by thread B, and thread B is blocked waiting
for a monitor owned by thread A.
This method is designed for troubleshooting use, but not for
synchronization control. It might be an expensive operation.
This method finds deadlocks involving only object monitors.
To find deadlocks involving both object monitors and
ownable synchronizers,
the findDeadlockedThreads method
should be used.
returns: an array of IDs of the threads that are monitor
deadlocked, if any; null otherwise. - `long[]`
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").get-all-thread-idsclj
(get-all-thread-ids this)Returns all live thread IDs. Some threads included in the returned array may have been terminated when this method returns.
returns: an array of long, each is a thread ID. - long[]
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").
Returns all live thread IDs.
Some threads included in the returned array
may have been terminated when this method returns.
returns: an array of long, each is a thread ID. - `long[]`
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").get-current-thread-cpu-timeclj
(get-current-thread-cpu-time this)Returns the total CPU time for the current thread in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy. If the implementation distinguishes between user mode time and system mode time, the returned CPU time is the amount of time that the current thread has executed in user mode or system mode.
This is a convenient method for local management use and is equivalent to calling:
getThreadCpuTime(Thread.currentThread().getId());
returns: the total CPU time for the current thread if CPU time
measurement is enabled; -1 otherwise. - long
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for the current thread.
Returns the total CPU time for the current thread in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy. If the implementation distinguishes between user mode time and system mode time, the returned CPU time is the amount of time that the current thread has executed in user mode or system mode. This is a convenient method for local management use and is equivalent to calling: getThreadCpuTime(Thread.currentThread().getId()); returns: the total CPU time for the current thread if CPU time measurement is enabled; -1 otherwise. - `long` throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for the current thread.
get-current-thread-user-timeclj
(get-current-thread-user-time this)Returns the CPU time that the current thread has executed in user mode in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy.
This is a convenient method for local management use and is equivalent to calling:
getThreadUserTime(Thread.currentThread().getId());
returns: the user-level CPU time for the current thread if CPU time
measurement is enabled; -1 otherwise. - long
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for the current thread.
Returns the CPU time that the current thread has executed in user mode in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy. This is a convenient method for local management use and is equivalent to calling: getThreadUserTime(Thread.currentThread().getId()); returns: the user-level CPU time for the current thread if CPU time measurement is enabled; -1 otherwise. - `long` throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for the current thread.
get-daemon-thread-countclj
(get-daemon-thread-count this)Returns the current number of live daemon threads.
returns: the current number of live daemon threads. - int
Returns the current number of live daemon threads. returns: the current number of live daemon threads. - `int`
get-peak-thread-countclj
(get-peak-thread-count this)Returns the peak live thread count since the Java virtual machine started or peak was reset.
returns: the peak live thread count. - int
Returns the peak live thread count since the Java virtual machine started or peak was reset. returns: the peak live thread count. - `int`
get-thread-countclj
(get-thread-count this)Returns the current number of live threads including both daemon and non-daemon threads.
returns: the current number of live threads. - int
Returns the current number of live threads including both daemon and non-daemon threads. returns: the current number of live threads. - `int`
get-thread-cpu-timeclj
(get-thread-cpu-time this id)Returns the total CPU time for a thread of the specified ID in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy. If the implementation distinguishes between user mode time and system mode time, the returned CPU time is the amount of time that the thread has executed in user mode or system mode.
If the thread of the specified ID is not alive or does not exist, this method returns -1. If CPU time measurement is disabled, this method returns -1. A thread is alive if it has been started and has not yet died.
If CPU time measurement is enabled after the thread has started, the Java virtual machine implementation may choose any time up to and including the time that the capability is enabled as the point where CPU time measurement starts.
id - the thread ID of a thread - long
returns: the total CPU time for a thread of the specified ID
if the thread of the specified ID exists, the thread is alive,
and CPU time measurement is enabled;
-1 otherwise. - long
throws: java.lang.IllegalArgumentException - if id <= 0.
Returns the total CPU time for a thread of the specified ID in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy. If the implementation distinguishes between user mode time and system mode time, the returned CPU time is the amount of time that the thread has executed in user mode or system mode. If the thread of the specified ID is not alive or does not exist, this method returns -1. If CPU time measurement is disabled, this method returns -1. A thread is alive if it has been started and has not yet died. If CPU time measurement is enabled after the thread has started, the Java virtual machine implementation may choose any time up to and including the time that the capability is enabled as the point where CPU time measurement starts. id - the thread ID of a thread - `long` returns: the total CPU time for a thread of the specified ID if the thread of the specified ID exists, the thread is alive, and CPU time measurement is enabled; -1 otherwise. - `long` throws: java.lang.IllegalArgumentException - if id <= 0.
get-thread-infoclj
(get-thread-info this id)(get-thread-info this id max-depth)(get-thread-info this ids locked-monitors locked-synchronizers)Returns the thread info for each thread whose ID is in the input array ids, with stack trace and synchronization information.
This method obtains a snapshot of the thread information for each thread including:
the entire stack trace,
the object monitors currently locked by the thread
if lockedMonitors is true, and
the
ownable synchronizers currently locked by the thread
if lockedSynchronizers is true.
This method returns an array of the ThreadInfo objects, each is the thread information about the thread with the same index as in the ids array. If a thread of the given ID is not alive or does not exist, null will be set in the corresponding element in the returned array. A thread is alive if it has been started and has not yet died.
If a thread does not lock any object monitor or lockedMonitors is false, the returned ThreadInfo object will have an empty MonitorInfo array. Similarly, if a thread does not lock any synchronizer or lockedSynchronizers is false, the returned ThreadInfo object will have an empty LockInfo array.
When both lockedMonitors and lockedSynchronizers parameters are false, it is equivalent to calling:
getThreadInfo(ids, Integer.MAX_VALUE)
This method is designed for troubleshooting use, but not for synchronization control. It might be an expensive operation.
MBeanServer access: The mapped type of ThreadInfo is CompositeData with attributes as specified in the ThreadInfo.from method.
ids - an array of thread IDs. - long[]
locked-monitors - if true, retrieves all locked monitors. - boolean
locked-synchronizers - if true, retrieves all locked ownable synchronizers. - boolean
returns: an array of the ThreadInfo objects, each containing
information about a thread whose ID is in the corresponding
element of the input array of IDs. - java.lang.management.ThreadInfo[]
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").
Returns the thread info for each thread
whose ID is in the input array ids, with stack trace
and synchronization information.
This method obtains a snapshot of the thread information
for each thread including:
the entire stack trace,
the object monitors currently locked by the thread
if lockedMonitors is true, and
the
ownable synchronizers currently locked by the thread
if lockedSynchronizers is true.
This method returns an array of the ThreadInfo objects,
each is the thread information about the thread with the same index
as in the ids array.
If a thread of the given ID is not alive or does not exist,
null will be set in the corresponding element
in the returned array. A thread is alive if
it has been started and has not yet died.
If a thread does not lock any object monitor or lockedMonitors
is false, the returned ThreadInfo object will have an
empty MonitorInfo array. Similarly, if a thread does not
lock any synchronizer or lockedSynchronizers is false,
the returned ThreadInfo object
will have an empty LockInfo array.
When both lockedMonitors and lockedSynchronizers
parameters are false, it is equivalent to calling:
getThreadInfo(ids, Integer.MAX_VALUE)
This method is designed for troubleshooting use, but not for
synchronization control. It might be an expensive operation.
MBeanServer access:
The mapped type of ThreadInfo is
CompositeData with attributes as specified in the
ThreadInfo.from method.
ids - an array of thread IDs. - `long[]`
locked-monitors - if true, retrieves all locked monitors. - `boolean`
locked-synchronizers - if true, retrieves all locked ownable synchronizers. - `boolean`
returns: an array of the ThreadInfo objects, each containing
information about a thread whose ID is in the corresponding
element of the input array of IDs. - `java.lang.management.ThreadInfo[]`
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("monitor").get-thread-user-timeclj
(get-thread-user-time this id)Returns the CPU time that a thread of the specified ID has executed in user mode in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy.
If the thread of the specified ID is not alive or does not exist, this method returns -1. If CPU time measurement is disabled, this method returns -1. A thread is alive if it has been started and has not yet died.
If CPU time measurement is enabled after the thread has started, the Java virtual machine implementation may choose any time up to and including the time that the capability is enabled as the point where CPU time measurement starts.
id - the thread ID of a thread - long
returns: the user-level CPU time for a thread of the specified ID
if the thread of the specified ID exists, the thread is alive,
and CPU time measurement is enabled;
-1 otherwise. - long
throws: java.lang.IllegalArgumentException - if id <= 0.
Returns the CPU time that a thread of the specified ID has executed in user mode in nanoseconds. The returned value is of nanoseconds precision but not necessarily nanoseconds accuracy. If the thread of the specified ID is not alive or does not exist, this method returns -1. If CPU time measurement is disabled, this method returns -1. A thread is alive if it has been started and has not yet died. If CPU time measurement is enabled after the thread has started, the Java virtual machine implementation may choose any time up to and including the time that the capability is enabled as the point where CPU time measurement starts. id - the thread ID of a thread - `long` returns: the user-level CPU time for a thread of the specified ID if the thread of the specified ID exists, the thread is alive, and CPU time measurement is enabled; -1 otherwise. - `long` throws: java.lang.IllegalArgumentException - if id <= 0.
get-total-started-thread-countclj
(get-total-started-thread-count this)Returns the total number of threads created and also started since the Java virtual machine started.
returns: the total number of threads started. - long
Returns the total number of threads created and also started since the Java virtual machine started. returns: the total number of threads started. - `long`
object-monitor-usage-supported?clj
(object-monitor-usage-supported? this)Tests if the Java virtual machine supports monitoring of object monitor usage.
returns: true
if the Java virtual machine supports monitoring of
object monitor usage;
false otherwise. - boolean
Tests if the Java virtual machine supports monitoring of
object monitor usage.
returns: true
if the Java virtual machine supports monitoring of
object monitor usage;
false otherwise. - `boolean`reset-peak-thread-countclj
(reset-peak-thread-count this)Resets the peak thread count to the current number of live threads.
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("control").
Resets the peak thread count to the current number of
live threads.
throws: java.lang.SecurityException - if a security manager exists and the caller does not have ManagementPermission("control").set-thread-contention-monitoring-enabledclj
(set-thread-contention-monitoring-enabled this enable)Enables or disables thread contention monitoring. Thread contention monitoring is disabled by default.
enable - true to enable; false to disable. - boolean
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support thread contention monitoring.
Enables or disables thread contention monitoring. Thread contention monitoring is disabled by default. enable - true to enable; false to disable. - `boolean` throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support thread contention monitoring.
set-thread-cpu-time-enabledclj
(set-thread-cpu-time-enabled this enable)Enables or disables thread CPU time measurement. The default is platform dependent.
enable - true to enable; false to disable. - boolean
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for any threads nor for the current thread.
Enables or disables thread CPU time measurement. The default is platform dependent. enable - true to enable; false to disable. - `boolean` throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for any threads nor for the current thread.
synchronizer-usage-supported?clj
(synchronizer-usage-supported? this)Tests if the Java virtual machine supports monitoring of
ownable synchronizer usage.
returns: true
if the Java virtual machine supports monitoring of ownable
synchronizer usage;
false otherwise. - boolean
Tests if the Java virtual machine supports monitoring of
ownable synchronizer usage.
returns: true
if the Java virtual machine supports monitoring of ownable
synchronizer usage;
false otherwise. - `boolean`thread-contention-monitoring-enabled?clj
(thread-contention-monitoring-enabled? this)Tests if thread contention monitoring is enabled.
returns: true if thread contention monitoring is enabled;
false otherwise. - boolean
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support thread contention monitoring.
Tests if thread contention monitoring is enabled.
returns: true if thread contention monitoring is enabled;
false otherwise. - `boolean`
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support thread contention monitoring.thread-contention-monitoring-supported?clj
(thread-contention-monitoring-supported? this)Tests if the Java virtual machine supports thread contention monitoring.
returns: true
if the Java virtual machine supports thread contention monitoring;
false otherwise. - boolean
Tests if the Java virtual machine supports thread contention monitoring.
returns: true
if the Java virtual machine supports thread contention monitoring;
false otherwise. - `boolean`thread-cpu-time-enabled?clj
(thread-cpu-time-enabled? this)Tests if thread CPU time measurement is enabled.
returns: true if thread CPU time measurement is enabled;
false otherwise. - boolean
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for other threads nor for the current thread.
Tests if thread CPU time measurement is enabled.
returns: true if thread CPU time measurement is enabled;
false otherwise. - `boolean`
throws: java.lang.UnsupportedOperationException - if the Java virtual machine does not support CPU time measurement for other threads nor for the current thread.thread-cpu-time-supported?clj
(thread-cpu-time-supported? this)Tests if the Java virtual machine implementation supports CPU time measurement for any thread. A Java virtual machine implementation that supports CPU time measurement for any thread will also support CPU time measurement for the current thread.
returns: true
if the Java virtual machine supports CPU time
measurement for any thread;
false otherwise. - boolean
Tests if the Java virtual machine implementation supports CPU time
measurement for any thread.
A Java virtual machine implementation that supports CPU time
measurement for any thread will also support CPU time
measurement for the current thread.
returns: true
if the Java virtual machine supports CPU time
measurement for any thread;
false otherwise. - `boolean`cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close