Object Request Broker custom properties

Specifies the domain name service (DNS) host name or IP address of the machine on which initial server contact for this client resides.

For a command-line or programmatic alternative, read the topic Client-side programming tips for the Object Request Broker service.

Specifies the port that the ORB uses to bootstrap to the machine on which the initial server contact for this client listens.

For a command line or programmatic alternative, read the topic Client-side programming tips for the Object Request Broker service.

The com.ibm.CORBA.ConnectTimeout property specifies the maximum time, in seconds, that the client ORB waits prior to timing out when attempting to establish an IIOP connection with a remote server ORB. Typically, client applications use this property. You can specify the property for each individual application server through the administrative console.

Begin with the default timeout value, but consider factors such as network congestion and application server load and capacity. Lesser values provide better failover performance in the case of extended problems with the remote server, such as downtime. Higher values are better for slow network or remote server performance. However, exceptions can occur if the remote server does not have enough time to complete the subsequent request. A value of 0 means that the ORB relies on the timeout set by the operating system TCP/IP layer. For most operating systems, the timeout is set to 75 seconds.

Specifies the connection interceptor class that is used to determine the type of outbound IIOP connection to use for a request, and if secure, the quality of protection characteristics associated with the request.

Specifies whether the ORB uses the locate request mechanism to find objects in a WebSphere Application Server cell. Use this property for performance tuning.

When this property is set to true, the ORB first sends a short message to the server to find the object that it needs to access. This first contact is called the locate request. If most of your initial method invocations are small, setting this property to false might improve performance because this setting change can reduce the GIOP traffic by as much as one-half. If most of your initial method invocations are large, you should set this property to true. When the property is set to true, the small locate request message is sent instead of the large locate request message. The large message is then sent to the target following the desired object is found.

Specifies the size of GIOP fragments that the ORB uses when it sends requests. If the total size of a request exceeds the set value, the ORB breaks the request into fragments, and sends each fragment separately until the entire request is sent. Set this property on the client side with a -D system property if you use a stand-alone Java application.

Adjust the value specified for the com.ibm.CORBA.FragmentSize property if the amount of data that is sent over IIOP in most GIOP requests exceeds 1 KB, or if thread dumps show that most client-side threads are waiting while sending or receiving data. Most messages should have few or no fragments.

If you want to instruct the ORB not to chunk any of the requests or replies it sends, set this property to 0. However, setting the value to zero does not prevent the ORB from receiving GIOP fragments in requests or replies sent by another ORB.

Specifies the port on which this server listens for incoming requests. This setting only applies for client-side ORBs.

Specifies the host name or IP address of the system on which the application server or client application ORB is running.

Specifies the number of concurrent TCP connections between the client and server Object Request Brokers. The default for this property is 1.

A value of 1 indicates that there will be at most only one connection between the client and each server ORB port. All the requests between the client and the server ORB will be multiplexed across those single connections. This can lead to a performance bottleneck in J2EE deployments where there are a large number of concurrent requests between the client and server ORBS.

Setting this value to a number greater than one <n> causes the client ORB to multiplex communications to each server ORB port over <n> multiple connections rather than a single connection. There will be no more than <n> concurrent sockets to each separate server ORB port at any one time. This can increase throughput under certain circumstances, particularly on a long-running, mulch-threaded client process. Since the number of parallel connections will never exceed the number of requesting client threads, the number of concurrent client request threads is therefore a sensible maximum limit for this property.

Specifies the number of JNI reader threads to be allocated in the JNI reader thread pool that is used by the ORB. Each thread can handle up to 1024 connections.

Specifies that JNI reader threads are used. The property name specifies the class name of the ORB component that manages the pool of JNI reader threads and interacts with the native OS library used to process multiple connections simultaneously.

Specifies an alternative to the default RAS manager of the ORB. This property must be set to com.ibm.websphere.ras.WsOrbRasManager prior to the ORB can be integrated with the rest of the RAS processing for the product.

Specifies whether the connection contexts, such as Partner Version, Sending Context Runtime, and Codebase contexts, are always sent with every GIOP message, or are sent only once for each connection.

When this property is set to always, all of the connection contexts are sent with every GIOP request and every GIOP response.

When this property is set to once, the connection contexts are only sent with the initial request.

Specifies the maximum number of connection requests that can be waiting to be handled by the Server ORB prior to the product starts to reject new incoming connection requests. This property corresponds to the backlog argument to a ServerSocket constructor and is handled directly by TCP/IP.

If you see a connection refused message in a trace log, typically, either the port on the target machine is not open, or the server is overloaded with queued-up connection requests. Increasing the value specified for this property can help alleviate this problem if there does not appear to be any other problem in the system.

Specifies that the exception detail message that is returned whenever the server ORB encounters a CORBA system exception contains a short description of the exception as returned by the toString method of java.lang.Throwable class. Otherwise, the message contains the complete stack trace as returned by the printStackTrace method of java.lang.Throwable class.

Specifies the class that the ORB uses to create SSL sockets for secure outbound IIOP connections.

Specifies the class that the ORB uses to create SSL sockets for inbound IIOP connections.

This property applies when you have a mixed release cluster for which you are performing an incremental cell upgrade, and at least one of the releases is earlier than Version 6.x.

In an environment that includes mixed release cells, the migration program automatically sets this property to 1.

Once you upgrade all of the cluster members to the same release, you can remove this property from the list of ORB custom properties, or you can change the value that is specified for the property to 2. Either action improves performance.

When this property is set to 1, the ORB runs using version 1 object identities, which are required for mixed cells that contain application servers with releases earlier than V6.x. If you do not specify a value for this property or if you set this property to 2, the ORB runs using version 2 object identities, which cannot be used with pre-V6.x application servers.

Use this custom property to specify the length of time in which the object request broker (ORB) waits for an available thread from the ORB thread pool prior to rejecting a request.

When the ORB receives an incoming request, the request is read by an ORB reader thread. The ORB reader thread attempts to hand off the request for processing by a worker thread in the ORB thread pool. When all the worker threads are handling other requests, the reader thread waits until a worker thread becomes available. While the reader thread is waiting, new requests are not processed by that particular reader thread. This situation can lead to deadlocks between the ORB thread pools on two different Java virtual machine (JVM) processes. The deadlocks are prominent when the ORB in one JVM process must call back to the ORB in the other JVM process to complete its request. Therefore, it is highly advisable to set this property to a positive non-zero value, which configures a finite wait period and can limit deadlock situations. However, configure the value for this custom property based on its effect on the average request processing time, the ORB request timeout value, and whether servers are making additional circular or backend calls.

Specifies the logical pool distribution (LPD) thread pool strategy that takes effect the next time you start the application server, and is enabled if set to com.ibm.ws.threadpool.strategy.LogicalPoolDistribution.

Some requests have shorter start times than others. LPD is a mechanism for providing these shorter requests greater access to start threads. For more information, read the Logical pool distribution topic.

Specifies how often the logical pool distribution (LPD) mechanism readjusts the pool start target times. This property cannot be turned off once this support is installed.

If you use this property, LPD must be enabled. Read the description of the com.ibm.websphere.threadpool.strategy.implementation property for more information.

Specifies, in milliseconds, how long the logical pool distribution internal data is kept for inactive requests. This mechanism tracks several statistics for each request type that is received. Consider removing requests that have been inactive for an unusually long length of time.

If you use this property, LPD must be enabled. Read the description of the com.ibm.websphere.threadpool.strategy.implementation property for more information.

Specifies how many pools are created and how many threads are allocated to each pool in the logical pool distribution mechanism.

The ORB parameter for specifying the maximum number of threads controls the total number of threads. The outqueues parameter is specified as a comma-separated list of percentages that add up to 100. For example, the list 25,25,25,25 sets up 4 pools, each allocated 25 percent of the available ORB thread pool. The pools are indexed left to right from 0 to n-1. The calculation mechanism dynamically assigns each outqueue a target start time. Target start times are assigned to outqueues in increasing order. Therefore, pool 0 gets the requests with the least start time, and pool n-1 gets requests with the highest start times.

If you specify this property, LPD must be enabled. Read the description of the com.ibm.websphere.threadpool.strategy.implementation property for more information.

Specifies that statistics are dumped to stdout once this interval expires, but only if requests are processed. This process keeps the mechanism from filling the log files with redundant information. These statistics are beneficial for tuning the logical pool distribution mechanism.

If you use this property, LPD must be enabled. Read the description of the com.ibm.websphere.threadpool.strategy.implementation property for more information.

Specifies the size of a new queue where incoming requests wait for dispatch. Pertains to the logical pool distribution mechanism.

If you use this property, LPD must be enabled. Read the description of the com.ibm.websphere.threadpool.strategy.implementation property for more information.

Prevents Location Service Daemon (LSD) related outgoing ORB calls from being invoked before the Security Service is initialized.

Sometimes Location Service Daemon (LSD) related outgoing ORB calls fail authentication because the calls are made before the server is ready to authenticate users. If you want the server to wait until the Security Service is initialized before invoking outgoing ORB calls, set this property to true.

The default value is false.

Specifies, in milliseconds, how frequently the server checks to see if the Security Service is up and running.

If you set the com.ibm.ws.orb.services.lsd.EnableSecurityServiceCheck custom property to true, use this property to indicate how frequently the server checks to see if the Security Service is up and running.

The default value is 5000 milliseconds, which is equivalent to 5 seconds.

Specifies the maximum number of times the server checks to see if the Security Service is up and running before issuing an error message that indicates that a Location Service Daemon (LSD) related outgoing ORB call failed authentication.

The default value is 10.

Specifies the maximum number of connections that the IIOP Tunnel Servlet maintains in its connection cache for each target host and port. If the number of concurrent client requests to a single host and port exceeds the setting for this property, the IIOP Tunnel Servlet opens a temporary connection to the target server for each extra client request, and then closes the connection once it receives the reply. Connections that are opened, but not used within 5 minutes, are removed from the cache for the IIOP Tunnel Servlet.

Specifies the number of seconds that the IIOP Tunnel Servlet waits for a reply from the target server on behalf of a client prior to timing out. If a value is not specified for this property, or is incorrectly specified, the com.ibm.CORBA.RequestTimeout property setting for the application server, on which the IIOP Tunnel Servlet is installed, is used as the setting for the com.ibm.ws.orb.services.redirector.RequestTimeout property.

The value you specify for this property must be at least as high as the highest client setting for the com.ibm.CORBA.RequestTimeout property; otherwise the IIOP Tunnel Servlet might timeout more quickly than the client typically times out while waiting for a reply. If this property is set to zero, the IIOP Tunnel Servlet does not timeout.

This custom property specifies a timeout value for reading Secure Sockets Layer (SSL) handshake-related messages.

When you set the com.ibm.ws.orb.transport.SSLHandshakeTimeout custom property to a positive integer value, the listener thread does not hang if a message is received following the specified timeout period. If you do not set this custom property or do not set it to a positive integer value, the timeout value defaults to 10000, a timeout period is not added, and the listener thread can hang.

Specifies whether the server ORB binds to all network interfaces in the system. If you specify true, the ORB binds to all network interfaces that are available to it. If you specify false, the ORB only binds to the network interface that is specified for the com.ibm.CORBA.LocalHost system property.

Specifies the name of the Java class that the product uses to implement the javax.rmi.CORBA.UtilDelegate interface.

This property supports delegation for method implementations in the javax.rmi.CORBA.Util class. The javax.rmi.CORBA.Util class provides utility methods that can be used by stubs and ties to perform common operations. The delegate is a singleton instance of a class that implements this interface and provides a replacement implementation for all of the methods of javax.rmi.CORBA.Util. To enable a delegate, provide the class name of the delegate as the value of the javax.rmi.CORBA.UtilClass system property. The default value provides support for the com.ibm.CORBA.iiop.noLocalCopies property.