Object Request Broker tuning guidelines

The following options exist for improving the performance of the Object Request Broker (ORB). Tuning results will vary among systems and applications.

• Logical Pool Distribution (LPD) mechanism

  If you suspect that requests with longer execution times are elongating the response times for shorter execution time requests by denying them adequate access to threads in the thread pool, LPD provides a mechanism to allow the shorter requests greater access to execution threads.

  For more information, see Logical Pool Distribution (LPD)

• ORB timeout

  If Web clients that access Java applications running in the product environment are consistently experiencing problems with their requests, and the problem cannot be traced to other sources and addressed through other solutions, consider setting an ORB timeout value and adjusting it for your environment.

  • Web browsers vary in their language for indicating that they have timed out. Usually, the problem is announced as a connection failure or no-path-to-server message.

  • Aim to set an ORB timeout value to less than the time after which a Web client eventually times out. Because it can be difficult to tell how long Web clients wait before timing out, setting an ORB timeout requires experimentation. Another difficulty is that the ideal testing environment features some simulated network failures for testing the proposed setting value.

  • Empirical results from limited testing indicate that 30 seconds is a reasonable starting value. Mainly, you need to ensure that the setting is not too low. To fine-tune the setting, find a value that is not too low. Then gradually decrease the setting until reaching the threshhold at which the value becomes too low. Set the value a little above the threshold.

  • When an ORB timeout value is set too low, the symptom is numerous CORBA 'NO_RESPONSE' exceptions, which occur even for some requests that should have been valid. If requests that should have been successful, for example, the server is not down, are being lost or refused, the value is likely to be too low.

  Note: Do not adjust an ORB timeout value unless experiencing a problem, because configuring a value that is inappropriate for the environment can itself create a problem. If you set the value, experimentation might be needed to find the correct value for the particular environment. Configuring an incorrect value can produce results worse than the original problem.

  You can adjust timeout intervals for the product's Java ORB through the following administrative settings:

  • Request timeout, the number of seconds to wait before timing out on most pending ORB requests if the network fails

  • Locate request timeout, the number of seconds to wait before timing out on a locate-request message

  • Connect timeout, the maximum time the client ORB waits before timing out while establishing an IIOP connection. See Object Request Broker service settings for more information.

• Determining the ORB message size

  The ORB breaks apart messages into fragments to send over the ORB connection. You can configure this fragment size through the com.ibm.CORBA.FragmentSize parameter.

  To determine the size of the messages being transferred over the ORB and the number of fragments required to do so, first enable ORB tracing in the ORB Properties page in the webui and then enable ORBRas tracing from the logging and tracing page in the webui. You'll probably also want to bump up the trace file sizes as this can generate a lot of data. Restart the server and run at least one iteration (preferably several) of the case you wish to measure.

  Then look at the traceable file and do a search for "Fragment to follow: Yes". This indicates that the ORB transmitted a fragment, but it still has at least one remaining fragment to send before the entire message has arrived. If No is indicated instead of Yes, this means that that particular fragment is the last in the entire message. It may also be the first if the message fit entirely into one fragment.

  If you go to the spot where "Fragment to follow: Yes" is located, you will find a block that looks similar to this:

  Fragment to follow:	Yes
  Message size:	4988 (0x137C)
  --
  Request ID:	1411

  This indicates that the amount of data in the fragment is 4988 bytes and the Request ID is 1411. Then if you do a search for all occurrences of "Request ID: 1411", you will see the number of fragments used to send that particular message. If you add all the associated message sizes, you will have the total size of the message that's being send through the ORB.

---

Logical Pool Distribution (LPD)

Tuning performance parameter index

Object Request Broker service settings in administrative console
    

 

---