When you are investigating an EAServer error, before you report the problem to Sybase Technical Support, gather the following information to expedite a solution:
Full text of error message and crash details, as appropriate.
Information about your EAServer installation:
Version number
Build number
Edition
This information appears at the start of the server log. See “Logging” for more information about log files.
Information about the EAServer process that is running in your environment, including version numbers of the DLLs or libraries loaded—see “ListDLLs”. To list which libraries are loaded and their load locations, use pmap, or a similar command for your platform.
Relevant log files, such as:
EAServer log
HTTP error log
HTTP request log
HTTP servlet log
See “Logging” for more information on log files.
Information about your platform:
Number of CPUs
Operating system version and patch levels
Memory
Environment variables, many of which are defined in the setup script setenv.sh (UNIX) or setenv.bat (Windows):
PATH
JAGUAR
SQLANY
CLASSPATH
BOOTCLASSPATH
LD_LIBRARY_PATH
JAGUAR_JDK12, JAGUAR_JDK13, and JAGUAR_JDK14
Not all the variables are defined in the setup script. The server and tools start-up scripts configure PATH, CLASSPATH, BOOTCLASSPATH and other settings.
Also check the user-defined scripts user_setenv.sh (UNIX) or user_setenv.bat (Windows) for additional settings.
See “Configuration issues” for more information on environment variables.
Information about the server JDK; including:
Java version (from the server log file)
VM type (from the server log file)
Other server properties that configure the Java VM
Database:
Database server
Database version/driver
Connection type (ODBC, JDBC, native)
Application information:
Nature of the application (for example, an order entry system)
Application type, client/server or Web application
Number of concurrent users that access the application during peak time
Maximum amount of data that the components retrieve
Amount of data returned to the clients
If service components exist, their function (verify that they are not transactional)
If shared components (versus multiple instance components) exist, their purpose
Whether components are being pooled
If stateful components exist, their function; also, whether SetComplete and SetAbort functions are called for these components
Types of components in use: PowerBuilder®, Web applications, servlets, JSPs, and so on
For applications that include PowerBuilder components, the number of:
PowerBuilder components used in the application
Whether any PowerBuilder components are invoked by a non-PowerBuilder client; and if so, the type of client
Whether the SetComplete and SetAbort functions are being called for stateful components, or whether the auto-demarcation deactivation component property is set for the components
