The supported versions of VMware vFabric tc Server are 2.6 to 2.9
To create VMware vFabric tc Server Monitor
To enable JMX in the tc Server, you have to define a JMX port in the file 'catalina.properties' and then give an entry in a server.xml
[Click the link to view an example server.xml file and also a snippet of catalina.properties which shows how to set values for the variables used in the server.xml file].
Applications Manager monitors the VMware vFabric tc Server and the Spring applications deployed on the server to detect any performance problems. This monitoring is carried out by tracking critical components of the vFabric tc Server such as memory, thread, throughput, garbage collector,etc.
The Availability tab shows the availability history of the vFabric tc Server for the past 24 hours or 30 days. The Performance tab shows some key performance indicators of the vFabric tc Server such as CPU utilization, throughput and garbage collection rate. This tab also shows the health status and events for the past 24 hours or 30 days.
The List view lists all the vFabric tc Servers monitored by Applications Manager along with their overall availability and health status. It enables you to perform bulk admin configurations. Click on the individual monitors listed to view detailed performance metrics.
To view detailed performance metrics of a vFabric tc Server, click on the monitor name listed in the Availability or List View tabs. The performance metrics have been categorized into 6 different tabs:
This tab provides a high-level overview of the health and performance of the vFabric tc Server along with information pertaining to the throughput, thread and garbage collection.
|Memory Used||The amount of memory used by the JVM|
|Memory available||The amount of physical memory available.|
|Used Heap||The percentage of heap memory space used.|
|Total Memory||Total amount of physical memory available to the operating system.|
|CPU Usage||The CPU utilization of the VM.|
|Bytes Received Per Second||The average bytes received per second.|
|Bytes Sent Per Second||The average bytes sent per second.|
|Error Count||The number of error request received.|
|Processing Time||The processing time taken to process the requests in milliseconds.|
|Request Count||The number of requests served by this global request processor.|
|Thread Count||Total number of threads created and also started since the Java virtual machine started.|
|Threads in Running State||Total number of threads executing in the Java virtual machine in running state.|
|Threads in Waiting State||Total number of threads in the Java virtual machine in waiting state.|
|Blocked Threads||A thread that is blocked waiting for a monitor lock is in this state.|
|Timed Waiting Threads||A thread that is waiting for another thread to perform an action, for up to a specified waiting time is in this state.|
|Deadlock Threads||Number of threads that are in deadlock waiting to acquire object monitors.|
|Eden Space||The pool from which memory is initially allocated for most objects.|
|Tenured Gen||The pool containing objects that have existed for some time in the survivor space.|
|Survivor Space||The pool containing objects that have survived GC of eden space.|
|Non Heap Memory|
|Perm Gen, Perm Gen [shared-rw], Perm Gen [shared-ro]||Holds all the reflective data of the virtual machine itself, such as class and method objects. With JVMs that use class data sharing, this generation is divided into read-only and read-write areas.|
|Code Cache||Memory used for compilation and storage of native code.|
|GC Rate||The rate of garbage collection.|
|Average GC Time (ms)||Time taken to perform garbage collection.|
You can use the Custom Fields option in the 'Monitor Information' section to configure additional fields for the monitor.
Support given for JDK 1.8:
When monitoring with JDK 1.8 MetaSpace, Applications Manager monitors and displays new memory space called MetaSpace and Compressed Class Space instead of the former Permanent Generation (Non-Heap).
This tab provides the details of the various applications running in the vFabric tc Server.
|Context||The various applications running.|
|Active Sessions||The number of sessions currently in active state.|
|Session Creation Rate||The number of sessions created per second.|
|Average Response Time||The average response time taken for a particular application.|
You can also disable, enable or delete a particular application by using the Actions option and also compare performance reports of different applications using theCompare Reports option.
This tab displays information pertaining to the number of requests received and sent per second in the server.
|Global Request Processor|
|Name||The name of the instances.|
|Bytes Received Per Second||The number of requests received per second in the server.|
|Bytes Sent Per Second||The number of requests sent per second from the server.|
|Error Count||The number of requests, not processed.|
|Processing Time ms||The time taken for a request to be processed in milliseconds.|
|Request Count||The total count of requests.|
This tab contains metrics related to cache memory
|Cache||The applications running in the server.|
|Access Count||The number of times the application is accessed.|
|Hits Count||The number of times the application is accessed from the cache.|
|Cache Hit Ratio %||The ratio of Hits Count to Access Count.|
This tab shows information pertaining to the database.
|Transaction Manager- Commits||The commit rate transactions per second and failed commits transactions.|
|Transaction Manager- Resumes||The resume rate transactions per second and failed resumes transactions.|
|Transaction Manager- Rollbacks||The rollback rate transactions per second and failed rollbacks transactions.|
|Transaction Manager- Suspends||The suspend rate transactions per second and failed suspends transactions.|
|Total Threads||The total number of threads started since the java virtual machine started.|
|Busy Threads||The number of threads currently busy.|
|Active Threads||The number of Active Threads in the JVM.|
|Max Threads||The maximum number of Threads in the JVM.|
|Pool Size||The number of objects in the pool (entity and stateless).|
|Requests Queue Size||The number of requests in the Request Queue.|
|Name||The Java virtual machine implementation name.|
|Version||The Java virtual machine Version.|
|JVM Vendor||The Java virtual machine implementation vendor.|
|Classpath||The Java class path that is used by the system class loader to search for class files.|
|Library Classpath||The Java library path.|
|Boot Classpath||The boot class path that is used by the bootstrap class loader to search for class files.|
|OS Name||The operating system name.|
|Total Memory (MB)||The amount of memory used by this VM.|
|Maximum Metaspace (MB)||The maximum Native memory space for the representation of class metadata is called Metaspace.MetaSpace use native memory Â to store meta-data and that grows automatically.|