A user can experience problems while trying to start a request or trying to get the status of a request in a model. For example, Connect CDC MonCon or Connect CDC Console may appear to wait for a long time (over 10 minutes) when you issue a command to start a request or get the status of a request. Similarly, a Connect command may appear to get no response in the Connect CDC MonCon Command History area.
For Connect CDC MonCon or Connect CDC Console to start a request or to get the status of a request, it must first issue a Connect command to the various hosts. On getting the Connect command, Connect CDC Listener tries to start the kernel process on that host.
If the memory specification for starting the kernel process is too big or too small, the kernel process does not start. Connect CDC Listener waits for 10 minutes for the kernel to start before giving up. The result is that there appears to be no response to the Connect command.
At the end of 10 minutes, there is an error message like this:
-ERR Timeout trying to start omnienterprise.oe.OmniCore <modelname>. See Connect CDC Listener log and check classpath. Check specified memory is not too big or too small. Here are a few possibilities to try out:
-
Run the installation kit. Check that the driver files are in the proper directory specified during installation. If the driver path is not correct, a detailed message will tell you the problem during verification stage of reconfiguration. Fix the problem and try again.
-
Check the startup scripts for the Connect CDC Listener for the classpath settings.
-
Check the memory settings.
-
Use reconfiguration to increase or decrease memory specifications and try again.