Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace WebSphere Liberty
Created by Guest
Created on Dec 2, 2024

COH Add Thread status log entries to Liberty code - Equivalent of TWas Runtime.ThreadMonitorHeartbeat

Traditional WebSphere had a configuration setting (Runtime.ThreadMonitorHeartbeat) that instructed it to log details about its thread pool usage e.g. the number of hung threads/size of the pool.

Liberty does not have this functionality.

Liberty only has one thread pool but it would still very useful to be able to see the history of the state of the threads.
This needs to be logged for support staff who are analysing the logs after an event to understand at what point the problem occurs.

These are the instructions for configuring this functionality for the traditional WebSphere system.

## Configuring the Websphere Thread Pool statistics to log key thread counts and their status ##
# Servers > Application Servers > Server Name > Troubleshooting > Logging and Tracing > Configuration > General Properties > Log Level Detail
:Runtime.ThreadMonitorHeartbeat=detail

 

Use case:
Who would use this?
support staff who need to:
Identify the state of the thread pool e.g. how many threads were hung at a particular moment in time

How frequently would it be used?
it would be used when investigating the health of a jvm and after a serious issue

Idea priority Urgent