If the server fails at a specific, reproducible point:
Verify that the server started correctly, as indicated by these console messages:
Accepting Connections: iiop://host:2000 Accepting Connections: iiops://host:2001 Accepting Connections: iiops://host:2002 The Management Console can be accessed at http://host:8000/console The Management Console can be accessed at https://host:8001/console Accepting Connections: http://host:8000 Accepting Connections: https://host:8001 Accepting Connections: https://host:8002 Server Started
where host is the EAServer host machine.
Check the server log for errors, to assess when the crash occurred, and to determine areas for further investigation.
In the Management Console, check the MessageProfiler tab to find out which components are active, the connections being used, and so on—see “Runtime monitoring tools”.
Using the information from steps 1 and 2, turn on debug and trace flags for specific components, connections, and so on.
Explore what is happening in the application or component. Look for common application trouble spots—see “Generic issues”.
Check the component and server property settings.
Debug the component.
Check the server configuration, specifically:
Patch levels—see “EAServer log” for details.
Resource and memory usage.
DLL versions, library versions, and Java class loading—see “Verifying your configuration” for library and class information, and “ListDLLs”.
Invoke a service component in the code just before where the crash is taking place to write information to the EAServer log—see “ListDLLs”:
JVM properties
Free and total memory
EAServer monitoring data
EAServer memory dump
Use the stack trace, dump file, and crash address for advanced troubleshooting—see “Stack traces, dump files, and core files”.
