The number of lines in the method used to process a custom tag exceeded 1000. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag = dd....dd, number of lines = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command
bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command
cc....cc: Path within the Web application of the concerned JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')
dd....dd: Custom tag name
ee....ee: Number of lines including the blank lines and comment lines of the method for processing the generated tag file

Description

In the case of the J2EE server mode or the cjjspc command

The number of lines of the method for processing the custom tag in the JSP file or tag file has exceeded 1000, including the comments and blank lines.

In the case of the servlet engine mode or the cjjsp2java command

The number of lines of the custom tag processing method coded in the JSP file has exceeded 1000, including the comments and blank lines.

Action

From the specifications of the Java virtual machine, the byte code of one method needs to be within 64 kilobytes. If the byte code of a method exceeds 64 kilobytes, it will result in an error during the generation of class file, or the exception java.lang.LinkageError will occur when the class is loaded.

If the size of one method is within 64 kilobytes, but is still extremely large, the following adverse effects might occur:

• A lot of time would be taken for GC processing.
• A lot of time would be taken for JIT compilation.
• A lot of memory would be consumed for JIT compilation.

As a result, the size of one method on the Java source is recommended to be within 500 lines, excluding comments and blank lines.

The number of lines of the Java code generated from the custom tag can be reduced by splitting the custom tag using dynamic include (include action).