Note: If you got trouble to start the server, check the error.log in logs/ directory. Usually it will show some usefull information.
- Please note that java compiler leaks memory each time it compiles. So if
you are using tools.jar for compile, eventually the system will run out of memory. If you plan to let your system up for a long time, use javac instead.
- CGI is not working. with server 0.95w and above, cgi is configurable. So if you are using your old web.xml, the config is not in there. User config servlet and edit the common server properties menu, and edit the cgi mapping. Add the default mapping /cgi/bin/ --> cgi/bin/ so
http://host/cgi/bin/test.txt will be mapped to cgi/bin/test.txt .
- Nothing shows up. What might happened is you have an older version of
servlet.jar. In the error.log usually it shows a exception about can't load
LocalString.properties in javax.servlet. The older servlet.jar could either in classpath or in your jdk\jre\lib\ext directory, where jdk is the directory you installed your jdk, or in \Program Files\JavaSoft\JRE\1.3.1\lib\ext if in windows (replace 1.3.1 with your java version).
You should either delete it or replace it with the newest version from sun (java.sun.com).
- Do not install the server in a directory which got a space char in its name,
example, "my servers", the server might not be able to start on windows. Also jsp files won't be able to compile.
- On windows platform, when request a jsp file for the first time, a dos prompt shows up. This problem will go away if you start the server from command prompt, so that the server got a console. On windows, jdk uses javaw.exe to start the jar file if you double click it, and jsp needs a java compiler to compile it on the first time, and the dos prompt will show up when the java compiler compile the jsp file. Don't worry, the client won't see it. You can also fix it by let java.exe instead of javaw when you click on the jar file.
- jsp not working. That is usually because you don't have jdk installed or javac is not in the path. If you don't have jdk installed, download the latest on from java.sun.com. Then use the config servlet to set the javac location.
First start the server, connect to http://localhost/srvConfig (it is case sensitive).
Click "Common Server Properties" on top left. You can find the filed "JSP compile string.", the default value is "javac -classpath jzHttpSrv.jar". Now change the javac part to full path (ie, if your javac is at c:\jdk1.3\bin\javac, then the new string will be "c:\jdk1.3\bin\javac -classpath jzHttpSrv.jar"). Click on the "save" button to save your settings.
- perl won't work. First, make sure your perl files are in "cgi\bin" directory.
Also, you need to have a perl interpter. If you perl.exe is in c:\perl\bin\perl.exe,
then put it in "Set perl interpreter location" box in common server properties (see above about how to get there).
- I am using Jview, and the jsp page can't find beans.
When used with older version of Microsoft JVM (jview) jsp bean loading will not work due to Microsoft's classloader implemention. In that case please upgrade to the newest version of the MS JVM.