July 10, 2011, 9:11 p.m.
posted by reo
Common Problems and Their Solutions
1 Cannot Start the Tomcat Server
"Out of Environment Space" Error. Symptom: An "out of environment space" error when running the startup and shutdown batch files in Microsoft Windows 9X/ME-based operating systems.
Solution: In the Microsoft Windows Explorer, right-click on the startup.batand shutdown.bat files. Select Properties, then select the Memory tab. Increase the Initial Environment field to something like 4096. Select Apply.
After you select Apply, shortcuts will be created in the directory you use to start and stop the container.
2 Compilation Errors
Ant Cannot Locate the Build File. Symptom: When you type antbuild, these messages appear:
Buildfile: build.xml does not exist! Build failed.
Solution: Start ant from the <JWSDP_HOME >/docs/tutorial/examples/gs/directory, or from the directory where you created the application. If you want to run ant from your current directory, then you must specify the build file on the command line. For example, on Microsoft Windows operating systems, you would type this command on a single line:
ant -buildfile C:\wspack1.0\docs\examples\src\gs\build.xml build
The Compiler Cannot Resolve Symbols. Symptom: When you type antbuild, the compiler reports many errors, including these:
cannot resolve symbol . . . BUILD FAILED . . . Compile failed, messages should have been provided
Solution: Make sure that you've set the JWSDP_HOME environment variable correctly. See Checking the Environment Variables (page 56).
3 Deployment Errors
Failure to Run Client Application. Symptom: The browser reports that the page cannot be found (HTTP 404).
Solution: The startup script starts the task in the background and then returns the user to the command line prompt immediately. Even though you are returned to the command line, the startup script may not have completely started Tomcat. If the Web client does not run immediately, wait up to a minute and then retry to load the Web client.
The localhost Machine Is Not Found. Symptom: The browser reports that the page cannot be found (HTTP 404).
Solution: Sometimes when you are behind a proxy and the firewall does not let you access the localhost machine. To fix this, change the proxy setting so that it does not use the proxy to access localhost.
To do this in the Netscape Navigator browser, select Edit -> Preferences -> Advanced -> Proxies and select No Proxy for: localhost. In Internet Explorer, select Tools -> Internet Options -> Connections -> LAN Settings.
The Application Has Not Been Deployed. Symptom: The browser reports that the page cannot be found (HTTP 404).
Solution: Deploy the application. For more detail, see Deploying the Application (page 62).