Writing Web Applications With WAI: Netscape Enterprise Server/FastTrack Server, Version 3.0/3.01

Error: WAI Application Not Found

Symptom: The web server cannot find your WAI application (for example, if it responds to an /iiop URI with a "Not Found" page).

Possible Explanation: Your WAI application is not properly registered with the web server. Try the following troubleshooting tips:

Verify that the application successfully registered with the web server. Check the return value of the function or method that registers the service. (In C, check the WAIregisterService() function. In C++ and Java, check the RegisterService method.)

Verify that you have passed the hostname and port of the web server to the WAIregisterService() function or the RegisterService method. The argument containing the hostname and port should specify this information in the following format:

   hostname:port_number

For example, the sample WASP and CAIIIOP examples retrieve the web server's hostname and port number from the command line (these examples expect you to enter this information as an argument).

Suppose you are running the web server on the machine named myhost on the port 80. To execute these applications, you enter the following commands:

   WASP myhost:80

   java -DDISABLE_ORB_LOCATOR WASP myhost:80

   CAIIIOP myhost:80

Verify that the web server is actually running on the specified host name and port.

If you are using a version 3.0 web server, run the osfind utility (under the server_root/wai/bin directory on UNIX and server_root\wai\bin directory on Windows NT) to see a list of the implementations running on your machine.

If you have set up the osagent utility to run on a specific IP address (or localhost, 127.0.0.1), you need to specify this address as a command-line parameter to the osfind utility. Use the -ORBagentaddr flag to specify this address.

For example, if the osagent utility is running on localhost (IP address 127.0.0.1), use this command to start osfind:

   osfind -ORBagentaddr 127.0.0.1

osfind returns information about any instances of osagent, OAD (the object activation daemon), and WAI applications running.

osfind: Found one agent at port 14000

   HOST: localhost

osfind: There are no OADs running on in your domain.

osfind: There are no Object Implementations registered with OADs.

osfind: Following are the list of Implementations started manually.

   HOST: 204.222.222.22

      INTERFACE NAME: netscape::WAI::WebApplicationBasicService

         OBJECT NAME: JavaWASP

      INTERFACE NAME: netscape::WAI::WebApplicationService

         OBJECT NAME: JavaWASP

      INTERFACE NAME: IDL:netscape/WAI/WebApplicationBasicService:1.0

         OBJECT NAME: JavaWASP

      INTERFACE NAME: IDL:netscape/WAI/WebApplicationService:1.0

         OBJECT NAME: JavaWASP

Verify that your object implementation appears in this list under the correct object name.

Go to the following URL to verify that your web service is registered under the built-in name service:

   http://hostname:port_number/NameService/WAS/service_name

If the server returns a page displaying the word IOR followed by some numbers, your service is registered.

For example, the WASP example provided with the web server registers under the service name WASP (for the C++ version) or JavaWASP (for the Java version). To verify that these applications register correctly, run the applications and go to the following URL:

   http://server:port/NameService/WAS/WASP (for C++)

   http://server:port/NameService/WAS/JavaWASP (for Java)

If the server returns a page containing the word IOR followed by a long string of numbers, your application has registered successfully to the web server.

If instead the server returns a "File Not Found" error, your service is not registered correctly.

Error: Server Error

Symptom: When you run your WAI application, you get a server error.

Possible Explanation: Server errors can occur for a number of different reasons. See the list of possible explanations below.

This type of problem may occur if you are running the object activation daemon (oad) while the web server's ORB is configured for localhost use only. (See the section "Configuring the Web Server's ORB" and Chapter 8, "Security Guidelines for Using WAI" for details.) You cannot run oad if the web server's ORB is configured this way.

Check the error log for messages. If a message similar to the following appears:

   [10/Aug/1997:22:52:51] failure: IIOPexec CORBA exception 
   CORBA::NO_IMPLEMENT.  Minor code: 0 Completed: NO

make sure that your WAI application is running.

The error log is stored in server-root/https-serverID/logs/errors.

Error: Invalid Stringified Object Reference `'

Symptom: When you attempt to run your WAI application, your application exits with the following error message:

Invalid Stringified Object Reference ''

Failed to Register with hostname

Possible Explanation: This error message can appear for a number of different reasons. See the list of possible explanations below.

If you are running one of the sample applications, make sure that you specify the hostname and port number as a command-line argument. For example:

   WASP myhost:80

Web Service Registration

The following two commands, unregobj and listimpl in the wai/bin directory are useful for troubleshooting whether you registered your web service properly.