Previous | Common Configuration Properties | Next |
The properties on the CORBA tab provide a view of the CORBA-related state of the services.
The current total of CORBA INITIALIZE exceptions thrown since the Service was started.
The current total of CORBA BAD_PARAM exceptions thrown since the Service was started.
The current total of CORBA INTERNAL exceptions thrown since the Service was started.
Number of active CORBA objects currently in service.
Number of CORBA objects purged from memory.
Timeout for CORBA object activity check, in seconds.
The current total of CORBA operations invoked.
Whether to load Singletons on server startup or on demand.
If set to TRUE (checked), this property enables the use of OpenFusion Dynamic Portable Interceptors for the Service.
Dynamic Portable Interceptors are required by an OpenFusion Service using adaptive load balancing with load shedding. See the Load Balancing Service Guide for details.
When set to TRUE this option enables the purging (deactivation) of objects from the server, limiting the amount of object references that are stored by the ORB. Objects may be purged at a given interval and/or when a maximum number of object references has been exceeded. Objects are purged using a least-recently-used algorithm.
The properties Object Cache Maximum Size and Object Cache Minimum Size are used to control object purging behaviour. These properties set upper and lower limits for the number of object references that the ObjectRegistry is expected to manage. Object purging will be triggered when the number of object references exceeds the Object Cache Maximum Size limit. The purging algorithm will attempt to destroy sufficient object references to reduce the number held in the ObjectRegistry to that specified by the Object Cache Minimum Size property.
For example, with the properties ObjectRegistry.MaxSize=1000 and ObjectRegistry.MinSize=100, purging will be triggered when the 1001st object reference is created. The purging algorithm will attempt to destroy 901 object references to reduce the numbr of references held in the ObjectRegistry to 100.
Note that memory usage does not correlate directly to the number of objects.
Naming Service: When the OpenFusion Naming Service is being used with object purging enabled, clients must always perform operations from the root context. Otherwise, problems will occur if the parents have been purged from memory.
This is the maximum number of objects that can be created in a server before purging occurs. When the object references handled by the ObjectRegistry exceeds the value of this property, objects are removed using a least-recently-used algorithm.
Objects will only be purged if Object Purging has be set TRUE. For full details of using this property, see Object Purging.
The minimum cache size for persistent CORBA objects. When objects are purged from the server, this number of objects will be left. For full details of using this property, see Object Purging.
This is the interval, in minutes, between object purge operations.
Objects will only be purged if Object Purging has be set TRUE.
This is a space separated list of arguments passed to the ORB at initialization.
This is the name of the POA (Portable Object Adaptor) created for the server. This property is only used by the VisiBroker 4.x and Orbix2000 distributions. Every server should have a unique POA name. The server UUID is used as the POA name when this field is left blank.
The server will run on a fixed port number when this option is set. The port number is that which the server will use to listen for requests.
A fixed port number allows for inter-ORB interoperability and enables servers to run without a daemon. Fixed ports also make it easier to implement security measures such as firewalls.
A unique identifier (UUID) associated with a specific server process. This ID is used to identify every object belonging to the process.
Previous | Common Configuration Properties | Next |