Appendix A       Troubleshooting


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

• Configuring the Class Path

• Setting up Transactions

• What Is a Lock Held by In-Doubt Error?

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.

Setting up Transactions

---

When configuring your resource manager for use in global transactions, you might encounter one or more of the following problems:

• What if xa_open Fails?

• What if xa_recover Fails?

• What Is a Lock Held by In-Doubt Error?

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

What if xa_open Fails?

If an xa_open failure message appears in your log file, you may have a problem with the open string. Global connections rely on open strings, which provide information for global transaction initialization. When installing iPlanet Application Server, the installation program puts default values in this open string. Check to be sure that the server name, user name and password are set correctly. for the appropriate open string format for your database

If you find an XAER_RMERR error, you have set the server instance incorrectly in the open string or the server is down.

If you find an XAER_INVAL error, there is a syntax error in your open string.

What if xa_recover Fails?

The following is an example of an xa_recover failure:

1 00271 99/04/30-10:00:28.124250 5c2c0837 W xa_recover to RM 0 returned x tCode -- 0xfffffffd (XAER_RMERR)

1 00271 99/04/30-10:00:28.124250 5c3c1017 W Terminating recovery scan for 0.

An xa_recover failure indicates that the database server is not set up for recovery. You must run the appropriate database setup script to create recovery tables and procedures.

For example, for Oracle databases, run the following scripts with sys permissions from the sqlplus prompt:

ftp://ftp1.iplanet.com/private/ias/60beta2/extra/xa_sql/xaviews.sql

ftp://ftp1.iplanet.com/private/ias/60beta2/extra/xa_sql/xaviews_add.sql

What Is a Lock Held by In-Doubt Error?

---

Global transactions are left "hanging" or in-doubt when a Java Server (KJS) process is abruptly killed or crashes. When the KJS process restarts, these transactions are rolled back, but if you want to manually delete them, refer to Resolving In-Doubt Transactions.

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 max_number_processes in the initinstancename.ora file in the pfile directory of the Oracle server installation.