Appendix A       Troubleshooting


This appendix contains the following information about troubleshooting iPlanet Application Server:

• Configuring the Class Path

• How Do I Configure the Number of Server-Side Connections?

Configuring the Class Path

When running applications, if the iPlanet Application Server Class Loader is unable to find the AppLogic class file through the SYSTEM_JAVA parameter (the registry parameter that contains both the CLASSPATH and GX_CLASSPATH settings) in the registry, iPlanet Application Server hands the request over to the Java Class Loader, which in turn reads the CLASSPATH environment variable to find the class file. This allows AppLogics and servlets to execute even if the user class path is not specified.

How Do I Configure the Number of Server-Side Connections?

Once a global transaction is started on a thread, a connection is tied to that thread. Therefore, when configuring the number of server-side connections, use the total number of Java Server (KJS) threads in your enterprise.

For example, for Oracle databases, change the value of processes in the initinstancename.ora file in the pfile directory of the Oracle server installation.