Filter
Top Products
The following table lists the threads created in Sterling B2B Integrator and their
source.
Thread created by Thread name Count
ActiveMQ ActiveMQ transport 80
ActiveMQ Session Task 11
Jetty SessionScavenger 47
ConduitStreamListener 16
SocketListener 10
JGroup Various Jgroup Handlers 22
JetSpeed RunnableThread 10
Perimeter PS Dispatcher Various Adapters 13
Business process queues ReschedulingThread 10
B2B B2B http Servlet Thread 3
FIFOTaskListener 10
QueueThread:queue 11
System RMI 7
Timer 7
Others From various components 30
Total 287
Controlling the Threads: Several threads created by Sterling B2B Integrator for
various purposes may not be required always and they can be controlled wherever
required. This will enhance the Sterling B2B Integrator performance considerably.
Following are the concepts described in this topic:
v ActiveMQ Threads
v Jetty Threads
v JGroup Threads
v JetSpeed Threads
v Adapter Threads
v Business Process Queue Threads
v FIFOTaskListener and Queue Threads
v RMI Threads
v Timer Threads
ActiveMQ Threads
ActiveMQ threads can be controlled by running ActiveMQ broker in a separate
JVM. No additional setup or configuration is necessary to run ActiveMQ in a
separate JVM. The Sterling B2B Integrator build installation process configures the
system to use it out of the box for both cluster ActiveMQ and non-cluster
ActiveMQ.
However, if you plan to use clustering, you may choose a different configuration
by editing the activemqconfig.xml file. Before editing this file, read the
Performance Management 197