Microservices Runtime Garbage Collection Test

In webMethods Microservices Runtime, the garbage collection (GC) cycle refers to the automated process by which the Java Virtual Machine (JVM) reclaims memory occupied by objects that are no longer in use by the application. This process is essential for maintaining efficient memory usage and preventing memory leaks in microservices environments. This test helps the administrators to monitor the number of freed objects in each garbage collection cycle since a very high count of freed objects indicates that a large portion of the allocated objects are no longer referenced and thus reclaimed during GC cycles. This situation can improve GC efficiency because the garbage collector spends less time marking and managing live objects, making the collection process faster.

Target of the test : webMethods Microservices Runtime

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each Garbage collection cycle in the target webMethods Microservices Runtime server.

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed
Host	The IP address of the target for which the test is to be configured.
Port	The port number at which the specified target listens to. By default, this will be 5555.
User and Password	Specify the credentials of a user who has the right to execute API commands on the target and pull out metrics. The specified user is the User who should possess Administator privileges and should be associated with the Logon as a Service policy.
Confirm Password	Confirm the password by retyping it here.
SSL	Set this flag to Yes, if the target being monitored is SSL-enabled.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Freed objects	Indicates the number of freed objects in this garbage collection cycle.	Number
Elapsed time	Indicates the elapsed time for this garbage collection cycle.	Minutes