Manage Object Request Brokers
Default property values are set when WAS is started and the Java ORB service is initialized. These properties control the run-time behavior of the ORB and can also affect the behavior of product components that are tightly integrated with the ORB, such as security. It might be necessary to modify some ORB settings under certain conditions.
In every request/response exchange, there is a client-side ORB and a server-side ORB. It is important that the ORB properties be set for both sides as necessary.
After an ORB instance has been established in a process, changes to ORB properties do not affect the behavior of the running ORB instance. The process must be stopped and cycled in order for the modified properties to take effect.
The following steps are to be performed only as needed.
- Adjust timeout settings to improve handling of network failures.
- Adjust thread-pool settings used by the ORB for handling IIOP connections.
- Use ORB custom property settings to enable and configure the Logical Pool Distribution (LPD) mechanism to improve performance on requests that have shorter execution times.LPD provides a mechanism allow shorter execution time requests greater access to execution threads. The LPD defaults are usually sufficient. However, when activating the LPD, it may be necessary to increase the ORB maximum thread pool size by 33 to 200 percent. Testing may be required to determine the best overall values for the ORB maximum thread pool size. Results will vary among systems and applications.
- If problems with the ORB arise, determine the problem.For help in troubleshooting, look at the ORB communications trace.
See Also
Object Request Brokers
Stopping servers
Starting servers
ORB tuning guidelines
ORB service settings in administrative console
ORB service settings that can be added to the administrative console
ORB communications trace
Client-side programming tips for the Java ORB service
Character codeset conversion support for the Java ORB service
ORB: Resources for learning