Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Sep 18, 2022

BPID shows active on queue watcher but UI shows terminated, some how the queue watcher JVM is out of synch with UI

I believe this being a bug or lack of functionality, Although this particular BPID was terminated from the UI then also via the command line -ControllerWorkFlow script but will not be remove from queue watcher! And also showed as terminated on UI.

At present, the only solution i to bounce the SI server. That is not the ideal solution since customer may not be restarting for months or quarter.

What is your industry? Life Sciences
How will this idea be used?

This functionality will bring consistency on the UI compare to what is shown on queue watcher.

  • Guest
    Sep 30, 2022

    Thank you for participating in the request for enhancement community. This scenario occurs when a thread in the JVM is unable to "stop". Controller Workflow only updates the database record, and does not issue a kill to the thread in the JVM. QueueWatcher is the most accurate as it reads from the JVM directly. The only way to troubleshoot this is through thread dumps and working with support on why the thread is stuck (usually in my experience its hung on the remote end of either a protocol or database connection)

    You can temporarily increase a thread in the queue if its block a thread, until restart can commence.