A Java Web server is a server that enables you to develop, test, and share server-side Java technologies, such as JavaServer pages and servlets. You might have to work with a Java Web server in order to complete your webAF projects.
webAF enables you to specify Java Web servers (including the default Java Web server), as well as to start or stop a Java Web server as needed. For more information, see the webAF online Help.
The default Java web server is used for all project types except Web application projects. Web application projects are associated with a Java Web server when the project is created. If you associate a Web application project with a custom Java Web server, and then delete that server, the project is unlikely to build.
The default Java Web server is started or stopped when you do not have a Web application project open and you select either Tools Services Start Java Web Server or Tools Services Stop Java Web Server.
Starting the default java web server with no project open will serve all the Web applications in the default project directory, likely resulting in an Out of memory
error.
You should always select Tools Services Stop Java Web Server to terminate the Debugger for a Web application project instead of selecting Debug Quit. This enables the Java Web server to perform an orderly shutdown.
You should always stop the Java Web server instead of terminating the DOS window. This enables the Java Web server to perform an orderly shutdown.
If the Web server does not stop as expected, the Web application is not recovering memory correctly, and the Web server must be aborted. Because of the number of objects involved with a typical Web application, such a memory leak has the potential to be quite large.
For more information about using the Java 2 Platform, Enterprise Edition (J2EE), see the webAF online Help.