If the server is slow to start, the problem may be the license manager, which may take one or two minutes to start.
If the server starts as expected, then slows down or runs out of memory, investigate these areas:
In the server log, search for “MEMORY MONITOR STATISTICS” to find the current Java memory usage and virtual memory usage.
In the Management Console, select Servers | <Server Name> | Statistics, and monitor the system to check pooling, peaks, maximums, sessions, and so on.
Check system sizing (virtual memory and paging file).
Use system tools to see which resource is failing. Check virtual bytes, CPU utilization, threads waiting, and so on. For each of these steps, see “Runtime monitoring tools”.
Review EAServer timeout properties. If no timeout is set, which is often the EAServer default, this leads to indefinite wait for transactions, components, or methods ().
Look for application trouble spots—see “Application issues”.
Check for memory leaks. For Java profiling, use Borland OptimizeIt. On Windows, use the Performance Monitor.
Implement a service component to periodically write information to the server log.
