To resolve or analyze a start-up crash:
Make sure that the PATH and CLASSPATH variables are correctly set.
Verify which DLL or library versions have been loaded, and class load locations. For Windows, see “ListDLLs”. For UNIX, use pmap or another command or tool appropriate for your platform.
If you are operating in a cluster environment:
Check cluster start-up/check settings.
Ensure all members have the same listener names and types.
Check the server log file. Besides reporting errors, the log file can also help determine how far along the start-up process was. The start-up tasks include:
Loading licensing files, check options
Loading network libraries for listeners
Initializing the JVM
Initializing various data structures
Loading server ClassLoader
Loading JCM (Java Connection Management) caches, connectors, and resources
Starting services:
Repository, GC, JCM, and Naming ServletService
User services; for example, the message service
If there are no problems, the server begins accepting regular client connections, as indicated by the console message “Accepting connections.”
In the server start batch file, set ECHO to on. This provides additional output and may help determine the point of failure.
Gather crash information, such as the load address. For Windows, see “ListDLLs”; for UNIX, use pmap or another command or tool appropriate for your platform.
When the server crashes, identify the crash address using the console or log file. Use the address to identify the crash area or the module being executed. When an executable is launched, it tends to use the same set of base addresses, as virtual addresses normally do not change. This helps determine the specific product or application to investigate. The address may show that the crash occurred outside of EAServer; for example, in a system module. If the crash occurred in EAServer or a Sybase module, the address may be helpful to Technical Support, and may point to a known issue.
If EAServer crashes while running as a service, start EAServer in a console instead. A service typically runs under different resource constraints and permissions than a console.
If the message service is configured, set cms.debug to true.
