Eliminating performance bottlenecks through JSP precompilation

Welcome to the "Management Corner" edition, the new Monthly column focuses on the management, configuration, processing, and development of WebLogic servers.

The purpose of this column is to introduce the problem of non-Java development that can be commonly used when using WebLogic sever. Developers and managers will also find this column valuable as they apply both to development and to the application of the final product. In addition, it has largely taken advantage of experience from the field and the Engineering laboratory, which provides detailed answers to practical questions.

The necessity of JSP pre-compiling

This article looks at removing the potential system performance bottleneck by solving one of the most common problems. The problem with the system overhead of JSP (JavaServer Page) compilation in Server run time, which puzzles almost all of the Java EE development plans. While JSP is the ideal choice for rendering Dynamic HTML views in the context of Java EE applications, they affect performance in a way that is more annoying than the wrong one, giving the first impression that the program is slow.

According to the Java EE specification, JSP is mainly an HTML file, in which the bread contains Java code to interact with other system components and dynamic display information. The specification stipulates that all the Java EE Application Server should support JSP, the customer requests a specific JSP, will:

Convert JSP to a servlet-type Java class (Java source format) from HTML format, replacing a fully compliant Java syntax with a shorthand JSP symbol

Compiles the newly generated Java source file into a. Class byte code form

Executes the appropriate interface method on the newly compiled class and returns a response to the client request.

Although from a development standpoint this is the best way to manage the creation of dynamic HTML within the presentation layer, it affects the server's run-time environment, requiring that the JSP be parsed, transformed into Java code, and compiled before it can handle a particular client request. The obvious effect on the end user is that a response will be delayed knowing that the given JSP file is compiled. Considering that a particular user request might use two or more JSP files, the time required to compile the state has increased many times.