Troubleshooting Rule Execution Server

Various paths are available for you in case of poor performance: you activate the execution unit (XU) log to study the execution trace, configure the XU memory profiler, explore database driver issues, or allocate more memory to applications.

To let a scalable number of users access resources through the Java™ components, Java connector architecture (JCA) assigns the task of implementing connection pooling to application server vendors.

If diagnostics are run before any execution units (XU) have been started, the test is passed and a message displays to report that no execution unit (XU) has been initialized.

On WebSphere® Application Server, the pool size is not instantiated beforehand. As a consequence, the server diagnostics cannot validate a Rule Execution Server before the first execution of a rule engine. The diagnostics remain useful to validate a configuration, especially in a cluster, and to check which execution units that are registered with the management model have been started.

For information on message strings, see Rule Execution Server messages.