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.
Note: - To let a scalable number of users access resources through the Java™ components, JCA assigns the
task of implementing connection pooling to application server vendors.
- If the diagnostics are performed 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.
- OnWebSphere® Application Server,
the pool size is not instantiated beforehand and therefore prevents
the server diagnostics from validating 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 registered with the management model have been
started.
For more general information, see Troubleshooting and support resources.
For information on message strings, see Rule Execution Server messages.