Object Request Broker services

Edit online

There are various settings that can be used to tune the internal Object Request Broker (ORB) processing.

ORB Thread Pool settings

A thread pool enables components of the server to reuse threads, which eliminates the need to create new threads at run time. Creating new threads expends time and resources.

In this case study:
  1. The maximum size of the ORB Thread Pool was increased from 50 to 1000 threads.
  2. The WAS was restarted.

WAS Administration console path: Servers > Application servers > server_name > Container Services > ORB service > Thread Pool Settings.

ORB fragmentation custom property

ORB fragmentation can be disabled by setting the CORBA fragmentsize set to zero. This helps to decrease FNP8 CPE CPU load and increase throughput.

However, if there are a lot of network packet retransmits in your environment it is not recommended to disable ORB fragmentation because the complete ORB request has to be resend.

In this case study:
  1. The value of com.ibm.CORBA.FragmentSize was set to zero.
  2. The WAS was restarted.

WAS Administration console path: Servers > Application servers > server_name > Container Services > ORB service > Custom Properties.

For more information about using the CORBA fragmentsize parameter for FileNet® P8, refer to the article Tune ORB in WebSphere® to boost FileNet P8 performance at this IBM® developerWorks® URL:
https://www.ibm.com/developerworks/data/library/techarticle/dm-1004tuneorbperformance/index.html