This is an IBM Automation portal for Integration 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
The updates discussed were added between ACEv12.0.7.0 and ACEv12.0.8.0 ... More details in the blog entry link below:
https://community.ibm.com/community/user/blogs/amar-shah1/2023/04/07/diagnosing-performance-issues-with-app-connect-mes
RFE Review. Thank you for raising this RFE and apologies for the time period it has been in Submitted Status. We agree this would be beneficial to the product and we are working on a plan for the integration server process to be able to trigger a FlowThreadReporter dump automatically if a flow thread takes too long to run, where "too long" could be defined by a user. We think this kind of improvement could help in cases where debugging flows inside a container (where remote administration can be harder). We also think some more traditional situations (database calls hanging, etc) might benefit from the server displaying exactly where the flow has become stuck. Attributes we are considering to expose on this new diagnostic would include:
Whether the capability is enabled
The Polling interval for checking the flow
The minimum age a thread must be running before taking action
Whether to create a dump of the flow history as well as its stack.
We are potentially considering this new diagnostic behaviour for both IIBv10 and ACEv11. Status of the RFE is updated to Planned for Future Release.
does Timeout events not help? it has a node trail like so....