Why is my Sterling B2B Integrator slow ?

This blog is designed to walk you through the process of pinpointing and resolving performance issues in a B2B Integrator.

Signs of a slow-performing application can manifest in different ways, including unusual

Queue Watcher:

In such a scenario, the initial step involves checking the accessibility of the Queue Watcher UI, which is the monitoring interface packaged with Sterling Integrator.

If the Queue Watcher responds, it serves as a valuable tool for pinpointing the root cause of the issue.

Utilized for comprehending the current internal activity of the primary B2B processing engine, the QueueWatch interface aids in the identification of problematic code and provides insights necessary for accurately tuning the application.

Access Queue Watcher by navigating to https://yourB2BServerHostname:Port/QueueWatch.

To gain insights into the ongoing processes, click on the first link titled “View Active Threads for All Queues.


From this point, you can observe all presently active processes, displayed at the bottom under “List of Working Threads,” along with the processing backlog indicated by “Queue Depth.”

In the provided illustration, 19 Business Processes are in queue 1, awaiting execution threads, with a maximum capacity of 1 thread. It is evident that the currently executing Business Process is sluggish, characterized by a substantial number of steps (i.e., 48034).

Queue Watcher Active Threads

Here’s another example below, illustrating a scenario where over 100,000 business processes are queued in queue 7. This queue is currently utilizing 80 execution threads out of a maximum capacity of 120:

Queue Watcher Depth, Sterling Integrator

Queueing is a standard practice in the application, serving the purpose of ensuring efficient workload processing within the limits of current system resources and the configured maximum global threads. These queues are adaptable and can be fine-tuned to give priority to specific tasks.

It is also possible to change the queues configuration dynamically in Queue Watcher without restarting the application (tip unknown to many users). The dynamic changes, obviously, will be lost after restart.

For lasting modifications to the queue configuration, ensuring persistence between restarts, employ the Performance Tuning Wizard accessible through the Dashboard interface (Operations/System/Performance/Tuning). These changes can be saved in costumer_overrides.properties to make them permanent.

Dynamic adjustments to the queues can aid in promptly clearing queues under specific circumstances.

Here’s how to dynamically alter the queues configuration:

Change Queue, Sterling integrator, Queue change, SII

To enhance parallel processing, it’s necessary to modify the queue configuration to allow for a greater number of threads to run concurrently. In the given example, the maximum number of threads for Queue 1 was adjusted from 1 to 10:

ChangeQDynamic, Sterling Integrator Queue watcher

Return to the “Active Threads for All Queues” page.

You should now notice the presence of multiple threads running concurrently:

Queue1 after changes, Sterling Integrator, Queue Watcher, SI, Pragma Edge

While this post won’t delve into the details of tuning system queues, the tip provided could prove highly beneficial in certain scenarios.

Now, let’s revisit the initial question: Why is the application experiencing slow performance?

If you observe that the Business Processes (BPs) are taking longer than usual, you can inspect the thread execution stack trace (second tip):

On the Queue Watcher main page, locate the option for “View Queue Threads”:

Queue Threads, Queue Watcher, Sterling integrator, SI

Subsequently, click on the “stacksize” link, identified as the 13th link in blue below:


Now, you can examine precisely what your Business Process (BP) is doing.

In the provided example, it is evident that the thread is in a TIMED WAITING state. By scrutinizing the method details, it becomes clear that the code is currently within the SleepyService.

QW Sleepy Service

In the second example below, it is apparent that the Business Process (BP) is engaged in performing some database operations:


Following this, you can refresh the stack trace page to ascertain whether the Business Process (BP) is progressing or consistently stuck in the same operation. This provides an initial insight into where to focus your investigation.

Slowness can have different causes like:

If the issue is pervasive, impacting all facets of the application, including the user interface (UI) and not solely restricted to Business Processes (BPs) and queueing, it is advisable to capture a few thread dumps of the application from the command line during the sluggish period.

Refer to this external link from the IBM website for instructions on how to take thread dumps:
Click Here

Top tip: Ensure to consistently check the application logs for any system errors.

Search for errors in critical categories such as Heap space, Out-of-Memory (OOM), JVM errors, database issues, file system (FS) problems, DNS errors, connectivity issues, and network errors within the application logs.

Initiate the investigation by examining logs related to noapp, system, sci, and perimeter if the slowness is pervasive across the entire system.

Verify the running threads using OS utilities:

In addition to utilizing administration interfaces, you have the option to directly identify executing processes through standard operating system utilities.

For Linux, employ the top process monitor with the command “top -H.” The “-H” switch alters the default view from top processes to top threads.

In the provided screenshot, the thread “WFE.37.Thread” is utilizing a significant portion of the CPU.


Leveraging OS tools like top offers a rapid way to pinpoint processes affecting your system. Have you observed the inclusion of workflow IDs in the thread names?


The ‘top‘ command is typically available in most Linux environments. For other operating systems, equivalents are generally accessible, though they may not always be included in standard builds.

If the top output is showing system threads rather than BP threads, always think of taking a few thread dumps of the application to share with customer support. And never forget to look at the application logs!

JMX monitoring:

An effective approach to identify the most resource-intensive application methods is through JMX (Java Management Extensions) monitoring.

Using SQL queries:

SQL queries can be instrumental in identifying long-running processes and steps within the application.

Previous Topic

Installing IBM Maximo APM - Asset Health Insights

Parent Topic

What's new in IBM Maximo APM - Asset Health Insights 7.6.1

Next Topic

Thank you for the Registration Request, Our team will confirm your request shortly.

Invite and share the event with your colleagues 

FileGPS - End To End File Monitoring

Subscribe to our newsletter

Elevate your approach to technology with expert-authored blogs, articles, and industry perspectives.

Thank You!

Thanks for signing up! We look forward to sharing resources and updates with you.

Continue to view our resources below.

Thank You!

Your Article submission request has been successfully sent. We will review your article & contact you very soon!

Sign up for Free Trail

Community manager solution extends IBM Sterling B2B Integrator to deliver next-generation B2B and File Transfer capabilities that meet the growing demands of the customer.

Thank You!

Thanks for contacting us. We will reach you shortly!

Select Industry & Watch IBM Partner Engagement Manager Demo

Start SRE Journey to AIOPs

FileGPS - End To End File Monitoring

Pragma Edge Jarvis Monitoring tool (Jarvis)

Thank you for submitting your details.

For more information, Download the PDF.

Community Manager - PCM

Community Manager - PCM

To deliver next-generation B2B and File Transfer capabilities

Pragma Edge - API Connect

IBM Partner Engagement Manager Standard

IBM Partner Engagement Manager Standard is the right solution
addressing the following business challenges

IBM Partner Engagement Manager Standard

IBM Partner Engagement Manager Standard is the right solution
addressing the following business challenges

IBM Partner Engagement Manager Standard

IBM Partner Engagement Manager Standard is the right solution
addressing the following business challenges

Thank you for the Registration Request, Our team will confirm your request shortly.

Invite and share the event with your colleagues 

Please Join us
On April 21 2021, 11 AM CT