If you encounter runtime problems with the engine, verify that logging is fully enabled. To do this, set "Engine Logging Level=DEBUG" on the Properties page for the runtime instance; this ensures that all messages are captured to the NNSYMessageLog.nml file. Also, verify that all other configuration information is correct.
Troubleshooting the runtime engine at runtime can be simplified by understanding the engine's three phases: capture, routing, and analysis. When evaluating the NNSYMessageLog.nml, check both the class reporting the message as well as the text of the message.
Refer to the following for specific troubleshooting information:
|
|
|
|
Error Message |
Engine's pid file exists but unable to create connection. |
|
Resolution
|
If you are using the Server Explorer, click to highlight the runtime instance and select Administration > Clean Run-Time Files. If you are using the clagent utility, run the abort_engine to remove the .pid file. syntax; [clagent] abort_engine -i <instance> |
|
|
|