Troubleshooting Repository Connection Problems

Waveset’s lh commands are very useful when you are troubleshooting connection problems. These commands use Waveset’s web application installation, but remove the application server from the equation.

This section describes the following

• Using lh Commands to Debug Problems

• Testing DataSource Connections

Using lh Commands to Debug Problems

This section describes how to use the lh commands; starting with using the more basic commands and progressing to using commands that exercise most of Waveset.

• Using lh setRepo -c -n

• Using lh setRepo -c -v

• Using setRepo

• Using lh console

After becoming familiar with these debugging tools, you can develop your own variations for using these lh commands.

Using lh setRepo -c -n

Use the lh setRepo -c -n command to perform the most basic connection test, which allows you to examine the current repository location without connecting. You can use this command to verify that parameters, such as URL and JDBC driver, are correct.

• If the connection is successful, you can read the ServerRepository.xml bootstrap file.

• If the connection fails, try to solve this failure first. A decryption error is the most common cause of this failure. For example, you might have a J2EE mismatch or classpath conflict.

Using lh setRepo -c -v

Use the lh setRepo -c -v command to connect to and examine the current repository location. (The -v provides verbose output.) You can use this command to exercise almost all of the Repository code without requiring the Waveset server.

• If the connection is successful, then you are successfully connected to the current repository location.

• If the connection fails, try to solve this problem first. Solving your connection problem can be very helpful in resolving DNS, firewall, or remote connection privilege problems.

For more information, see Testing DataSource Connections.

Using setRepo

Use the setRepo command throughout the debugging process, to specify a new repository location or to set the repository to the same location.

You can use this command to confirm that all of the necessary components, such as the JAR files, are in place. The setRepo command also lets you vary connection information, such as userid and password, to debug table ownership or privilege problems.

Using lh console

Use this command to actually start an Waveset Server using the JAR files in the WEB-INF/lib and the classes in WEB-INF/classes under WSHOME. The lh console command uses your Waveset installation environment and actually starts the Waveset application, but removes the application server from the equation.

• If the connection is successful, the problem is specific to the application server environment or configuration.

• If the connection fails, review the failure messages.

• If the connection failure is the same as the application server failure, you have reproduced this failure with significantly fewer variables.

• If the failure appears to be different from the application server failure, try fixing the Waveset connection problem first because there are fewer variables and more of these variables are under Waveset control.

Testing DataSource Connections

If you are testing a DataSource connection, the lh setRepo -c command might fail.

This failure is especially likely if you configured Waveset to use the application server’s database connectivity service or the application server’s directory service. These services often work only in the environment that a running application server provides to a web application.

Initially, approach the DataSource configuration you want in a step-by-step manner. Once you are comfortable with these steps, you can adapt your approach to suit your needs.

1. Try using a direct JDBC DriverManager connection, such as a non-DataSource connection, that bypasses the application server’s database connectivity service.

2. Use a DataSource, but store the DataSource object in a directory service other than application server’s directory service.

   ---

   Note –

   If you have no other directory service available, you can download a free directory service, including the reference implementation of JNDI that uses only the local file system.

   ---

   If these steps work, you have localized the problem to the application server.

   Then, if useful, you can add the application server’s database connectivity service or the application server’s directory service, whichever service works outside of the environment that the application server provides to web applications.