Additional Live Collaboration Server Configuration Troubleshooting

If performance problems or server shutdown persist after changing settings resulting from the server startup configuration checker, there are other areas you can check. Performance problems and server shutdown can be caused by improper configuration settings resulting in insufficient memory. Problems can occur if memory requirements that change due to objects cached in memory grow to exceed the amount of allocated memory within a Java Virtual Machine or even the entire system. Other problems may contribute, such as lack of disk space or inadequate memory for a machine's current load. It is sometimes difficult to determine the source of these problems. Environments vary in type of application server, platforms, server machine specifications, and operating system versions, to name some of the obvious configuration components.

Related Topics
Checking Disk Space
Checking Memory Usage
Checking for Other Running Processes

When problems occur after you have diagnosed your system with the configuration checker, you should check your system for these potential problem areas:


  • Checking Disk Space
  • Checking Memory Usage
  • Checking for Other Running Processes
  • Reviewing Other Configuration Issues
  • Collecting Logs and Core Files

Collecting logs and cores file is optional and needs to be performed only if the problem has not been resolved using the previous procedures.

Tables in this section may contain a column entitled "Category". Settings in these tables fall into one of three categories:


  • Critical
  • Warning
  • Information

The category refers to the level of priority that should be given to the particular setting. For example, if a setting is referred to as Critical, the ENOVIA Live Collaboration Server should not be run if the setting either does not exist where it should appear or it is outside the minimum range specified in the table. Settings that are Warnings should be set within the minimum range of values in the table. Information settings have the lowest priority but have been known to cause problems. In other words, they may not be a problem in a particular environment, but they should not be ignored.

The guidelines described in this section are intended to provide basic methods for investigating and resolving performance and quality-of-services issues. Recommended settings may not always result in better performance and may require further tuning.