Verify that you can ping your connection cache.
Check the deployment properties of the application’s components. See Chapter 14, “Importing and Exporting Application Components,” in the EAServer System Administration Guide for information about deploying components.
Look for Java classes loading from unexpected locations. Class loader logging is enabled by com.sybase.jaguar.server.jvm.verbose.
You can find all occurrences of a class in BOOTCLASSPATH and CLASSPATH using the ClassSearch utility, which is described in TechNote 1017251, ClassSearch Utility,.
Verify that maximums and limits are set appropriately for the production environment:
EAServer properties (caches, sessions, threads, and so on)
JVM
Ensure that the listener ports are not already in use and that no two EAServer listeners are defined to use the same port number.
Check that the versions of the PBVM on the server and the PowerBuilder client match. Check all files, especially libjcc.dll, which may be shipped with both PowerBuilder and EAServer releases, ESDs, and EBFs.
EAServer includes libjcc.dll in
the EAServer dll directory. PowerBuilder
may include the file as well, in the %SYBASE_SHARED%/PowerBuilder directory,
since this file is needed on PowerBuilder client installations.
Sybase recommends that you not copy the libjcc.dll provided
with PowerBuilder to the server as part of a PBVM setup.
Even if you have the latest PowerBuilder patch, use the EAServer libjcc.dll.
Problems can result if either the EAServer application server or EAServer Manager uses a different version than its own (such as the one provided with PowerBuilder). This used to be a problem when EAServer looked at the system path variable. However, now that EAServer sets up the path in the serverstart script, the problem is less likely to occur; users must modify either the script or environment to cause the problem.
If you specify the CacheName in the dbparm property of the transaction object, make sure you check the Enable Cache-By-Name access box.
Verify that LD_LIBRARY_PATH includes:
$JAGUAR/lib:$SQLANY/lib:$JAGUAR/intersolv/lib $JAGUAR/jdk/jdk_latest/lib/sparc/libthread/5.5.1 $JAGUAR/jdk/jdk_latest/lib/sparc/native_threads $LD_LIBRARY_PATH
Add the location of the X-Window xterm utility to your PATH variable. For example:
set path = ($path /usr/bin/x11/)
Verify that the THREADS_FLAG variable is either not set or is set to “native_threads.”
If you cannot start the server, verify that these environment variables are properly set:
PATH – must include $JAGUAR/bin.
JAGUAR – specifies the location of the EAServer installation directory.
SQLANY – specifies the location of the Adaptive Server Anywhere directory.
If the PATH or CLASSPATH settings do not include the required directories, or if the settings are too long, you may experience problems.
The %JAGUAR%\bin\serverstart.bat and %JAGUAR%\html\classes\jagmanager.bat files modify the PATH and CLASSPATH variables. Look at these files to investigate problems with either of these variables.
