Server Startup Configuration Checker

This topic describes diagnostics that the automated configuration checker performs when a kernel is started.

The automated configuration checker provides error messaging that can help you troubleshoot your server environment. If after running the configuration checker you still experience performance or server shutdown problems, refer to Additional Live Collaboration Server Configuration Troubleshooting.

See Also
mxAudit.log File
Evaluation Details

An automated configuration checker reports on common 3DSpace configuration problems that can cause severe performance degradation or server shutdowns. The checker writes diagnostic information to an mxAudit.log file. Users can also view diagnostic information via the MQL Print Config command. See the MQL Concepts for details.

When the kernel loads, its initialize function calls the configuration checker, which evaluates the settings listed below. Topics or headings in the following table have a link to the topic that describes it.

Setting Checked Category Error Range
JVM Settings for Application Server
-Xms Critical !=Xmx
-Xmx Critical <256M
-Xss Critical <384K
-XX:NewSize Warning >0.45*Xmx || <0.50*Xmx
-XX:MaxNewSize Warning !=NewSize
-XX:SurvivorRatio Warning !=2
Other Java Settings
Obsolete versions of eMatrixServletXXX.jar Critical
JVM Mode Critical !=Server Mode
Java Version Critical <1.3.1
Key ENOVIA Live Collaboration Environment Variables
MX_CONNECTION_POOL_SIZE Critical ==1
MX_CONNECTION_POOL_SIZE Warning <10
MX_PROGRAM_POOL_SIZE Warning <10
MX_MAX_THREAD Warning <200
MX_TRANSACTION_TIMEOUT Warning not set
MX_ABORT_DANGLING_TRANSACTION Critical !=TRUE
MX_MEMORY_SYSTEM_LIMIT Critical not set
Trace Settings Warning

-XX settings apply to Sun's JVM only. These warnings should be ignored when using WebSphere's JVM.

Each setting is evaluated by the configuration checker, which reports diagnostic information using the following categories:

  • Informational--information-only messages that might be useful when tracking down performance issues and minor problems
  • Warning--messages indicating that a setting could cause a problem and should be corrected
  • Critical--messages alerting that a setting will cause a problem and must be changed

These messages can be viewed using the mxAudit.log file or the MQL Print Config command.