Set custom properties for the ORB service

 

+

Search Tips   |   Advanced Search

Use the administrative console to add custom properties to the Object Request Broker (ORB) service. To set custom properties, follow these steps:

1. Go to...

   administrative console | Servers | Applicaiton Servers |servername | ORB Service

2. On the ORB Service page, click Custom Properties.

3. To add a custom property, follow these steps:

   1. Click New.

   2. Specify a name and value for the property. You can also specify a description.

   3. If you want to specify another property, click Apply and then specify the name and value for the next property.

   4. After you specify the custom property or properties, click OK.

4. Save the configuration.

Note: The Custom Properties page might include Secure Sockets Layer (SSL) properties that are added during installation.

You can add any of these custom properties to manage the ORB service:

• com.ibm.CORBA.FragmentSize

  Size, in bytes, of General Inter-ORB Protocol (GIOP) fragments that the ORB uses. If the total size of a request exceeds the specified value, the ORB breaks the request into smaller fragments and sends each fragment separately until the entire request is sent. If you are running a stand-alone Java application, it is recommended that you set this property on the client side with a -D system property.

  You might want to change this property if the amount of data that is sent over IIOP exceeds 1k. It is recommended that you change this property if thread dumps show that most client-side threads are stuck in a wait coming from writeLock. Sometimes a small amount of fragmentation is acceptable, so the parameter should be set such that most messages have few to no fragments.

  The default value is 1024. Valid values range from 64 to largest value of Java int type that is divisible by 8.

• com.ibm.CORBA.ListenerPort

  Port on which the server listens for incoming requests. This property is valid only for client-side ORBs. The default value is the next available system-assigned port number. Valid values range from 0 to 2147483647.

• com.ibm.CORBA.LocalHost

  Host name or IP address of the system on which the server ORB is running. By default, the ORB obtains a value at run time by calling InetAddress.getLocalHost().getHostAddress(). This property is valid only for client-side ORBs.

• com.ibm.CORBA.ServerSocketQueueDepth

  This property corresponds to the length of the TCP/IP stack listen queue and prevents WebSphere Application Server from rejecting requests when there is not space in the listen queue. If several clients connect simultaneously to the server-side ORB, you can increase this parameter to support up to 1000 clients. The default value is 50, and values can range from 50 to the largest value of Java int type.

• com.ibm.CORBA.ShortExceptionDetails

  When the server ORB encounters a CORBA system exception, it returns an exception detail message. If this property is set to any value, this detail message contains a short description of the exception as returned by the toString() method of java.lang.Throwable. By default, the message contains the complete stack trace as returned by the printStackTrace() method of java.lang.Throwable.

• com.ibm.websphere.threadpool.strategy.implementation

  If you set this property set to com.ibm.ws.threadpool.strategy.LogicalPoolDistribution, this property enables the Logical Pool Distribution (LPD) thread pool strategy the next time you start the application server. Some requests have shorter processing times than others. LPD is a mechanism for allowing these shorter requests greater access to the available threads. For more information, see Logical Pool Distribution.

• com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.calcinterval

  How often, in milliseconds, the LPD mechanism readjusts the pool target processing times. The property cannot be turned off after this support is installed. The default value is 30, and the minimum value is 20000.This property has no effect if LPD is not enabled.

• com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.lruinterval

  Specifies the length of time, in milliseconds, that LPD retains internal data for inactive requests. The mechanism tracks several statistics for each request type received. It is recommended that you remove inactive requests. The default value is 300000, and the minimum value is 60000. This property has no effect if LPD is not enabled.

• com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.outqueues

  How many pools are created and how many threads are allocated to each pool in LPD. The ORB parameter for max threads controls the total number of threads. The outqueues propery specifies a comma separated list of percentages that must add up to 100. For example, the list 25,25,25,25 sets up 4 pools. Each pool contains 25% of the available ORB thread pool. The pools are indexed left to right from 0 to n-1. Each outqueue is dynamically assigned a target processing time by the calculation mechanism. Target execution times are assigned to outqueues in increasing order so pool 0 gets the requests with the least execution time and pool n-1 gets requests with the highest execution times. The default value is 25,25,25,25. This property has no effect if LPD is not enabled.

• com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.statsinterval

  If you specify this property, statistics are dumped to stdout after the specified interval if requests have been processed. This property prevents LPD from saving redundant information to the log files. These statistics can help you tune LPD. The default value is 0 milliseconds, which means that the property is disabled. Specify a value of 30000 or greater. This property has no effect if LPD is not enabled.

• com.ibm.websphere.threadpool.strategy.LogicalPoolDistribution.workqueue

  Size of a new queue where incoming requests wait to be dispatched. The default value is 96, and the minimum value is 10. This property has no effect if LPD is not enabled.