Administration guide > Tune and performance > ORB properties and file descriptor settings
Enable NIO or ChannelFramework on the ORB
WebSphere eXtreme Scale provides a server property to set the TransportMode property to ChannelFramework in order to enable non-blocking I/O (NIO) on the Object Request Broker (ORB).
Before you begin, find the existing server properties file or create a server properties file. You can enable the ChannelFramework transport mode on the catalog service and on container servers.
Currently, you can run with NIO or ChannelFramework in WXS standalone scenarios.
To run with NIO on the IBM ORB, set the TransportMode property of the IBM ORB to ChannelFramework.
By default, the IBM ORB runs in Pluggable mode. WXS provides a server property to set the TransportMode property to ChannelFramework.
WAS only supports Pluggable mode in current releases. When WXS runs integrated with WAS, it must follow the Pluggable mode. Because WXS also uses the WAS SSL/Transport Security, it also currently supports Pluggable mode only.
- Add the enableChannelFramework=true property to the server properties file.
- Verify the server properties file does not contradict the ORB properties file.
If the server properties file enables the ChannelFramework value on the TransportMode property, but the TransportMode property is set to Pluggable in the orb.properties file, the server does not override the orb.properties file setting. A warning message displays in the log that indicates that two settings exist.
To allow the enableChannelFramework=true property to take effect, adjust properties that indicate the TransportMode property is set to Pluggable. In the orb.properties file, change...
...or remove the property.
- Provide the updated server property file at catalog service or container server startup.
When a catalog service or container server uses the channelFramework TransportMode, the following message is in the log:
CWOBJ0052I: The IBM ORB TransportMode property was set to ChannelFramework
If you see the following message in the log, examine the ORB properties:
CWOBJ0055W: The IBM ORB TransportMode property was set to ChannelFramework in the server properties file, but the existing orb.properties file already had a TransportMode set. The TransportMode will not be overridden.
Note that when you enable the ChannelFramework setting, the maximum value for the com.ibm.CORBA.ServerSocketQueueDepth property is 512. If the value for the com.ibm.CORBA.ServerSocketQueueDepth property in the orb.properties file is higher than 512, the server automatically sets the com.ibm.CORBA.ServerSocketQueueDepth property value to 512 and notifies you by printing an informational message to the log. No action is required.
CWOBJ0053I: The IBM ORB ServerSocketQueueDepth property was set to 512 to run with correctly with the ChannelFramework TransportMode.
Parent topic:Configure Object Request Brokers
Parent topic:ORB properties and file descriptor settings
ORB properties and file descriptor settings
Use the ORB with stand-alone WXS processes
Configure a custom Object Request Broker
ORB properties file