Converts an integer to a Unicode Decimal in a char array
-
+
Overflow can happen if the resulting External Decimal value does not fit into the char array, given the offset and
precision.
Converts a long to a Unicode Decimal in a char array
-
+
Overflow can happen if the resulting Unicode Decimal value does not fit into the char array, given its precision
and offset .
@@ -2679,7 +2679,7 @@
C
A management interface of the CRaC functionality in the Java virtual machine.
Returns the filename to use for writing out a heap dump, either based
- on what the user has set or by generating the default name based on the
+ on what the user has set or by generating the default name based on the
image name
Fetches an array of the native (operating system assigned) identifiers
+
Fetches an array of the native (operating system assigned) identifiers
corresponding to unique TIDs (as returned by java/lang/Thread.getId()) specified to it.
Used to determine if a property has been set in the context property
diff --git a/api/jdk17/index-files/index-9.html b/api/jdk17/index-files/index-9.html
index e7ee697210..49fe430c46 100644
--- a/api/jdk17/index-files/index-9.html
+++ b/api/jdk17/index-files/index-9.html
@@ -630,7 +630,7 @@
This method returns the total CPU usage for all application threads.
- It includes the threads that are in the "Application" category as well as those in the user defined categories (Application-UserX).
+ It includes the threads that are in the "Application" category as well as those in the user defined categories (Application-UserX).
This does not include information about "Resource-monitor" threads.
if cd is non- null, returns a new instance of
diff --git a/api/jdk17/jdk.management/com/ibm/lang/management/JvmCpuMonitorMXBean.html b/api/jdk17/jdk.management/com/ibm/lang/management/JvmCpuMonitorMXBean.html
index e90360078d..9317b88482 100644
--- a/api/jdk17/jdk.management/com/ibm/lang/management/JvmCpuMonitorMXBean.html
+++ b/api/jdk17/jdk.management/com/ibm/lang/management/JvmCpuMonitorMXBean.html
@@ -104,7 +104,7 @@
Interface JvmCpuMonitorM
"Resource-Monitor" threads are special because they do not participate in idle accounting.
This means that any CPU usage of these threads does not count towards determining the state of the application.
A thread can be part of only one category at any given time but can change categories any number of times during its timeline.
-
The usage information is in microseconds and increases monotonically.
+
The usage information is in microseconds and increases monotonically.
The CPU usage information consists of the following data:
Attached threads that are live.
@@ -122,7 +122,7 @@
Interface JvmCpuMonitorM
- This information is based on repeatedly checking the CPU usage in the following use case scenarios:
+ This information is based on repeatedly checking the CPU usage in the following use case scenarios:
Monitoring application idle and active behavior.
Calculating the JVM Overhead over a specific interval.
@@ -143,7 +143,7 @@
The OpenJ9 interface for managing and monitoring the virtual machine's memory pools.
- The following list describes 4 common behavior changes for MemoryPoolMXBean.
- You can revert to the earlier implementation of MemoryPoolMXBean by setting the
+ The following list describes 4 common behavior changes for MemoryPoolMXBean.
+ You can revert to the earlier implementation of MemoryPoolMXBean by setting the
-XX:+HeapManagementMXBeanCompatibility Java command line option.
-
+
The following names are reported for heap memory pools, listed by garbage collection policy:
@@ -133,19 +133,19 @@
1. More detailed heap memory pools can be obtained by calling MemoryPoolMXBean.getUsage() or MemoryPoolMXBean.getCollectionUsage().
- In some cases the total sum of memory usage of all heap memory pools is more than the maximum heap size.
+ In some cases the total sum of memory usage of all heap memory pools is more than the maximum heap size.
This irregularity can be caused if data for each pool is collected between garbage collection cycles,
where objects have been moved or reclaimed.
- If you want to collect memory usage data that is synchronized across the memory pools, use the
+ If you want to collect memory usage data that is synchronized across the memory pools, use the
GarbageCollectionNotificationInfo or GarbageCollectorMXBean.getLastGcInfo() extensions.
-
+
The usage threshold attribute is designed for monitoring the increasing trend of memory usage and incurs only a low overhead.
This attribute is not appropriate for some memory pools.
- Use the MemoryPoolMXBean.isUsageThresholdSupported() method to determine
+ Use the MemoryPoolMXBean.isUsageThresholdSupported() method to determine
if this functionality is supported by the memory pool to avoid an unexpected UnsupportedOperationException.
The following names are reported for heap memory pools that support the usage threshold attribute:
@@ -157,11 +157,11 @@
- The collection usage threshold is a manageable attribute that is applicable only to some garbage-collected memory pools.
- This attribute reports the amount of memory taken up by objects that are still in use after a garbage collection cycle.
- Use the MemoryPoolMXBean.isCollectionUsageThresholdSupported() method to determine
+ The collection usage threshold is a manageable attribute that is applicable only to some garbage-collected memory pools.
+ This attribute reports the amount of memory taken up by objects that are still in use after a garbage collection cycle.
+ Use the MemoryPoolMXBean.isCollectionUsageThresholdSupported() method to determine
if this functionality is supported by the memory pool to avoid an unexpected UnsupportedOperationException.
The following names are reported for heap memory pools that support the collection usage threshold attribute:
diff --git a/api/jdk17/jdk.management/com/ibm/lang/management/MemoryUsageRetrievalException.html b/api/jdk17/jdk.management/com/ibm/lang/management/MemoryUsageRetrievalException.html
index 2f7535bece..4a84fa62e6 100644
--- a/api/jdk17/jdk.management/com/ibm/lang/management/MemoryUsageRetrievalException.html
+++ b/api/jdk17/jdk.management/com/ibm/lang/management/MemoryUsageRetrievalException.html
@@ -87,7 +87,7 @@
Class MemoryUsageR
public class MemoryUsageRetrievalExceptionextends Exception
-
Exception class whose instance is thrown when Memory usage sampling fails.
+
Exception class whose instance is thrown when Memory usage sampling fails.
For exact cause one needs to inspect the exception string message capturing
the details by calling the toString() method.
Returns the native process identifier that identifies the current
- Java process to the operating system. The value is prone to being
- recycled over a period of time, as considered suitable by the
+ Java process to the operating system. The value is prone to being
+ recycled over a period of time, as considered suitable by the
operating system.
Returns:
-
A long representing the process ID (pid) on the underlying
+
A long representing the process ID (pid) on the underlying
operating system.
@@ -247,7 +247,7 @@
getProcessID
getVMGeneratedCPULoad
doublegetVMGeneratedCPULoad()
-
Returns a system load average calculated over the minute preceding
+
Returns a system load average calculated over the minute preceding
the call averaged over the number of CPU available to Java virtual
machine process.
Fetches an array of the native (operating system assigned) identifiers
+
Fetches an array of the native (operating system assigned) identifiers
corresponding to unique TIDs (as returned by java/lang/Thread.getId()) specified to it.
Fetches an array of the native (operating system assigned) identifiers
+
Fetches an array of the native (operating system assigned) identifiers
corresponding to unique TIDs (as returned by java/lang/Thread.getId()) specified to it.
Find the native (operating system assigned) thread identifiers corresponding
- to a unique TID (as returned by java/lang/Thread.getId()). When querying multiple threadIDs,
+ to a unique TID (as returned by java/lang/Thread.getId()). When querying multiple threadIDs,
consider using getNativeThreadIds(long[]) as it is more efficient than getNativeThreadId().
Parameters:
@@ -190,7 +190,7 @@
getNativeThreadId
ID is no longer alive or does not exist, -1 is returned.
SecurityException - is thrown if the caller does not have sufficient permissions
+
SecurityException - is thrown if the caller does not have sufficient permissions
(ManagementPermission("monitor"))
@@ -207,7 +207,7 @@
dumpAllExtendedThreads
threads in the virtual machine during the time it is invoked.
Fetches an array of ExtendedThreadInfo objects that provide native thread
identifiers along with java.lang.management.ThreadInfo object representing the thread.
- Consider using dumpAllExtendedThreads() in place of dumpAllThreads() as it provides
+ Consider using dumpAllExtendedThreads() in place of dumpAllThreads() as it provides
additional thread identification information in an efficient manner.
Parameters:
@@ -220,11 +220,11 @@
dumpAllExtendedThreads
Returns:
Array of ExtendedThreadInfo objects.
Throws:
-
SecurityException - is thrown if the caller does not have sufficient permissions
+
SecurityException - is thrown if the caller does not have sufficient permissions
(ManagementPermission("monitor"))
UnsupportedOperationException - is thrown if the JVM does not support monitoring
object monitor usage or ownable synchronizer usage, even as it has been specified.
-
InternalError - is thrown in case an error occurs while fetching thread information,
+
InternalError - is thrown in case an error occurs while fetching thread information,
typically, an internal error resulting from an inconsistency in the class library.
The maximum number of file descriptors that can be opened in a process or
- -1, if an error occurred while obtaining this. If the operating system doesn't have
+ -1, if an error occurred while obtaining this. If the operating system doesn't have
any limits configured, Long.MAX_VALUE is returned.
Deprecated, for removal: This API element is subject to removal in a future version.
Returns the native process identifier that identifies the current
- Java process to the operating system. The value is prone to being
- recycled over a period of time, as considered suitable by the
+ Java process to the operating system. The value is prone to being
+ recycled over a period of time, as considered suitable by the
operating system.
threads in the virtual machine during the time it is invoked.
Fetches an array of ExtendedThreadInfo objects that provide native thread
identifiers along with java.lang.management.ThreadInfo object representing the thread.
- Consider using dumpAllExtendedThreads() in place of dumpAllThreads() as it provides
+ Consider using dumpAllExtendedThreads() in place of dumpAllThreads() as it provides
additional thread identification information in an efficient manner.
Specified by:
@@ -237,9 +237,9 @@
dumpAllExtendedThreads
Returns:
Array of ExtendedThreadInfo objects.
Throws:
-
InternalError - is thrown in case an error occurs while fetching thread information,
+
InternalError - is thrown in case an error occurs while fetching thread information,
typically, an internal error resulting from an inconsistency in the class library.
-
SecurityException - is thrown if the caller does not have sufficient permissions
+
SecurityException - is thrown if the caller does not have sufficient permissions
(ManagementPermission("monitor"))
UnsupportedOperationException - is thrown if the JVM does not support monitoring
object monitor usage or ownable synchronizer usage, even as it has been specified.
The maximum number of file descriptors that can be opened in a process or
- -1, if an error occurred while obtaining this. If the operating system doesn't have
+ -1, if an error occurred while obtaining this. If the operating system doesn't have
any limits configured, Long.MAX_VALUE is returned.
public class GuestOSInfoRetrievalExceptionextends Exception
-
This exception class is thrown when retrieving
+
This exception class is thrown when retrieving
Guest (Virtual Machine(VM)/Logical Partition(LPAR)) usage statistics fails.
It could be trying to retrieve either GuestOSProcessorUsage or
GuestOSMemoryUsage. For exact cause one needs to inspect the exception
diff --git a/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSMXBean.html b/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSMXBean.html
index a3417f47a1..6ed8502572 100644
--- a/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSMXBean.html
+++ b/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSMXBean.html
@@ -126,7 +126,7 @@
Function instantiates a GuestOSProcessorUsage object and populates it with the
- current snapshot of Processor Usage statistics of the Guest as seen by the Hypervisor.
+ current snapshot of Processor Usage statistics of the Guest as seen by the Hypervisor.
The statistics are an aggregate across all physical CPUs assigned to the Guest by the Hypervisor.
if cd is non- null, returns a new instance of
diff --git a/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSProcessorUsage.html b/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSProcessorUsage.html
index 0fbfb7546c..0f8bde647d 100644
--- a/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSProcessorUsage.html
+++ b/api/jdk17/jdk.management/com/ibm/virtualization/management/GuestOSProcessorUsage.html
@@ -137,7 +137,7 @@
if cd is non- null, returns a new instance of
diff --git a/api/jdk17/jdk.management/com/ibm/virtualization/management/HypervisorMXBean.html b/api/jdk17/jdk.management/com/ibm/virtualization/management/HypervisorMXBean.html
index 9d6d66a96c..05c7b81cb5 100644
--- a/api/jdk17/jdk.management/com/ibm/virtualization/management/HypervisorMXBean.html
+++ b/api/jdk17/jdk.management/com/ibm/virtualization/management/HypervisorMXBean.html
@@ -131,7 +131,7 @@
Function instantiates a GuestOSProcessorUsage object and populates it with the
- current snapshot of Processor Usage statistics of the Guest as seen by the Hypervisor.
+ current snapshot of Processor Usage statistics of the Guest as seen by the Hypervisor.
The statistics are an aggregate across all physical CPUs assigned to the Guest by the Hypervisor.
Reset the JVM dump options to the settings specified when the JVM was started removing any additional
- configuration done since then. This method may throw a ConfigurationUnavailableException if the dump
- configuration cannot be altered. If this occurs it will usually be because a dump event is currently being
+ configuration done since then. This method may throw a ConfigurationUnavailableException if the dump
+ configuration cannot be altered. If this occurs it will usually be because a dump event is currently being
handled.
This function sets options for the dump subsystem.
- The dump option is passed in as a String. Use the same syntax as the -Xdump command-line option, with the
- initial -Xdump: omitted. See the -Xdump option section on dump agents in the
+ The dump option is passed in as a String. Use the same syntax as the -Xdump command-line option, with the
+ initial -Xdump: omitted. See the -Xdump option section on dump agents in the
documentation for the OpenJ9 JVM. This method may throw a ConfigurationUnavailableException if the dump
configuration cannot be altered.
@@ -244,7 +244,7 @@
triggerDump
A java dump is in a human-readable format, and summarizes the state of the JVM.
The default heap dump format (a phd file) is not human-readable.
A system dump is a platform-specific file that contains information about the active processes, threads, and
- system memory. System dumps are usually large.
+ system memory. System dumps are usually large.
The snap dump format is not human-readable and must be processed using the trace formatting tool supplied with the OpenJ9 JVM.
Parameters:
@@ -268,7 +268,7 @@
triggerDumpToFile
The JVM will attempt to write the file to the specified file name. This may
include replacement tokens as documented in the section on dump agents
in the documentation for the OpenJ9 JVM.
-
+
A string containing the actual filename written to is returned. This may not
be the same as the requested filename for several reasons:
@@ -283,7 +283,7 @@
triggerDumpToFile
to write the dump to another location, unless -Xdump:nofailover was specified on
the command line.
-
+
If a security manager exists a permission check for com.ibm.jvm.DumpPermission will be
made, if this fails a SecurityException will be thrown.
Reset the JVM dump options to the settings specified when the JVM was started removing any additional
- configuration done since then. This method may throw a ConfigurationUnavailableException if the dump
- configuration cannot be altered. If this occurs it will usually be because a dump event is currently being
+ configuration done since then. This method may throw a ConfigurationUnavailableException if the dump
+ configuration cannot be altered. If this occurs it will usually be because a dump event is currently being
handled.
This function sets options for the dump subsystem.
- The dump option is passed in as a String. Use the same syntax as the -Xdump command-line option, with the
- initial -Xdump: omitted. See the -Xdump option section on dump agents in the
+ The dump option is passed in as a String. Use the same syntax as the -Xdump command-line option, with the
+ initial -Xdump: omitted. See the -Xdump option section on dump agents in the
documentation for the OpenJ9 JVM. This method may throw a ConfigurationUnavailableException if the dump
configuration cannot be altered.
@@ -235,7 +235,7 @@
triggerDump
A java dump is in a human-readable format, and summarizes the state of the JVM.
The default heap dump format (a phd file) is not human-readable.
A system dump is a platform-specific file that contains information about the active processes, threads, and
- system memory. System dumps are usually large.
+ system memory. System dumps are usually large.
The snap dump format is not human-readable and must be processed using the trace formatting tool supplied with the OpenJ9 JVM.
Specified by:
@@ -258,7 +258,7 @@
triggerDumpToFile
The JVM will attempt to write the file to the specified file name. This may
include replacement tokens as documented in the section on dump agents
in the documentation for the OpenJ9 JVM.
-
+
A string containing the actual filename written to is returned. This may not
be the same as the requested filename for several reasons:
@@ -273,7 +273,7 @@
triggerDumpToFile
to write the dump to another location, unless -Xdump:nofailover was specified on
the command line.
-
+
If a security manager exists a permission check for com.ibm.jvm.DumpPermission will be
made, if this fails a SecurityException will be thrown.
getPid()instead.