Migrated enterprise application fails to install on WebSphere Application Server V5.0 due to error compiling JSP files
 Technote (troubleshooting)
 
Problem(Abstract)
After migrating your enterprise application from a previous version of WebSphere® Application Server, to V5.0, your application fails to install. Following migration, the JSP files fail to compile due to an unresolved symbol. The error message, ADMA5004E, is seen in the WASPostUpgrade.log
 
Cause
The enterprise archive (EAR) file did not install during migration as a result of the JSP files not compiling. The JSP file does not compile indicating that it cannot find a class that is in the class directory.

The following is a snippet from the WASPostUpgrade.log file:

ADMA6010I: The tasks are [com.ibm.ws.management.application.task.ExtractionTask, com.ibm.ws.management.application.task.CompileJspTask, com.ibm.ws.management.application.task.ConfigureTask, com.ibm.ws.management.application.task.BackupAppTask]
ADMA5016I: Installation of MYModule started.
ADMA6013I: Extract application binaries at C:\DOCUME~1\thomro00\LOCALS~1\Temp\app_f2b8f68cde\ear
ADMA5009I: Application archive extracted at C:\DOCUME~1\thomro00\LOCALS~1\Temp\app_f2b8f68cde\ear
Compiling jsps in MYModule.war
Invoking compilation ..
...
JSPG0042I: Code generation successful for /MyJSP.jsp.
...
JSPG0045I: Compiling...
C:/DOCUME~1/thomro00/LOCALS~1/Temp/app_f2b8f68cde/ear/MYModule.war/WEB-INF/classes/_MyJSP.java:73: cannot resolve symbol
symbol  : class MYClass  
location: class org.apache.jsp._MyJSP
MYClass efsrf = new MYClass();

Note: Some input files use or override a deprecated API.
Note: Recompile with -deprecation for details.
1 errors
Errors compiling jsps in C:\DOCUME~1\thomro00\LOCALS~1\Temp\app_f2b8f68cde\ear\MYModule.war
Return code from jsp-compilation is: 1
ADMA5004E: Jsps in war MYModule.war could not be compiled, check logs for more errors.: com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in compiling jsps - MYModule.war (rc=1)
Exception in jsp compile: com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in compiling jsps - MYModule.war (rc=1)
ADMA6012I: Exception in run com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in compiling jsps - MYModule.war (rc=1)
Exception: com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in compiling jsps - MYModule.war (rc=1)
com.ibm.websphere.management.exception.AdminException: ADMA0021E: Error in compiling jsps - MYModule.war (rc=1)
at
com.ibm.ws.management.application.task.CompileJspTask.compileWar(CompileJspTask.java:125)
at
com.ibm.ws.management.application.task.CompileJspTask.performTask(CompileJspTask.java:67)
at
com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:216)
at java.lang.Thread.run(Thread.java:512)
ADMA6011I: Deleting directory tree C:\DOCUME~1\thomro00\LOCALS~1\Temp\app_f2b8f68cde
ADMA5011I: Cleanup of temp dir for app MYModule done.
ADMA5014E: Installation of application MYModule failed.
WASX7017E: Exception received while running file "C:\WebSphere\Backup2\install_MYModule"; exception information: com.ibm.bsf.BSFException: error while eval'ing Jacl expression: com.ibm.ws.scripting.ScriptingException: WASX7132E: Application install for C:\WebSphereAE\AppServer\installableApps\MYModule.ear failed: see previous messages for details.
MIGR0340E: Unable to deploy the application MYModule.

Classes used in the JSP file require an explicit import of the class.
 
Resolving the problem
It is preferable to put the classes in a named package and have the JSP file import the package. After making this change, reinstall the EAR.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Servlet Engine/Web Container
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1111129
IBM Group: Software Group
Modified date: Feb 28, 2005