Product: OpenFusion CORBA Services

Version: ALL 

Description:

Startup of Name Service and Notification Service takes about 4 minutes.

Resolution:

The services may take a while to re-start. When re-starting these performs two things:

1. The re-activation of all persistent objects. For the Notification Service it makes sure all the event channel factory and all channels, admins and proxies are restored. For the Name Service it restores all the bound names and contexts.

2. Re-delivery of outstanding persistent events. (Notification Service) The event channel factory (queue manager) instructs all channels (queues) to perform recovery. Each channel/queue goes to the database and gets an array of all events; i.e. all persistent events that were not delivered before the service stopped. If there are events, the channel makes sure that all delivery queues (proxy suppliers) are fully initialized, and then pushes each outstanding event to each delivery queue in turn. If you have a lot of channels, admins and proxies or names and contexts then the services will take longer to restart. A good comparison is to try starting the Time Service and see how long this takes. This is a very basic server. If this takes a long time it could be down to hardware/ and or your environment.

The GUI can also be slow, depending on the Windows Manager and the performance of the machine.

There are a number of command line tools that you can use to bypass the manager altogether. Basically these are the server script which you can use to start, stop and query the status of the servers and the AdminMgrTool which allows you to manipulate the XML files without using the manager. You can find details of these in the System Guide and also in their usage command.