Problems using the JavaServer Pages (JSP) engine
If you are having difficulty using the JavaServer Pages (JSP) engine, try these steps:
Extension Processor [class com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor] was initialized successfully. Extension Processor [class com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor] has been associated with patterns [*.jsp *.jspx *.jsw *.jsv ].If the JSP processor fails to load, you will see a message such as
No Extension Processor found for handling JSPs. JSP Processor not defined. Skipping : jspfilename.in the server log files.
Message: /filename.jsp(2,1)JSPG0076E: Missing required attribute page for jsp element jsp:includeThis example indicates that line 2, column 1 of the named JavaServer Pages file is missing a mandatory attribute for the jsp:include action. Similar messages are displayed for other syntax errors.
The error message output from the Javac compiler will be found in the server log files. It might look like:
JSPG0091E: An error occurred at line: 2 in the file: /myJsp.jsp JSPG0093E: Generated servlet error: c:\WASROOT\temp\ ... test.war\_myJsp.java:16: myInt is already defined in com.ibm.ws.jsp20._myJsp int myInt = 122; String myString = "number is 122"; static int myStaticInt=22; int myInt=121; ^ 1 error
Correct the error in the JSP file and retry the file.
JavaServer Pages fail to compile when using precompile
Symptom | JavaServer Pages fail to compile during deployment through the administrative
console when precompile is selected.SystemErr R com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in compiling jsps - xyz.war (rc=1) |
Problem | JavaServer Pages fail to compile during deployment through the administrative console when precompile is selected when there is a dependency on another Java archive (JAR) file that is not available on any class path. |
Recommended solution | You may use wsadmin scripting to precompile JSP files during enterprise
application deployment. However if you want to use the administrative console,
then compile all JSP files before packaging the application.
|
If none of these steps solves the problem, check to see if the problem is identified and documented using the links in Diagnosing and fixing problems: Resources for learning.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.