Troubleshooting
Problem
The jdkSourceLevel is changed when installing the application EAR with 2.3 version web.xml and select the "Precompile JSPs" option during the deployment. The deployment process checks for the web module version to set the jdkSourceLevel to match with the web module version. This causes the jdkSourceLevel to change to a different value other than the default value, and sometimes causes the JSPs to fail to compile.
Symptom
Cannot access the application due to the JSP compile error.
Diagnosing The Problem
When a JSP fails to compile, check the jdkSourceLevel parameter in the {WAS_ROOT}/profiles/profilename/config/cells/cellname/applications/enterpriseappname/deployments/deployedname/webmodulename/ibm-web-ext.xml file and make sure it is set to the correct level. The following are some jdkSourceLevel parameter values:
- 15 - This value will enable the use of the assertion facility and will disable all new language features of JDK 6.0 and JDK 7.0.
- 16 - This value will enable the use of the assertion facility and will disable all new language features of JDK 7.0.
- 17 - This value will enable the use of the new features of JDK 7.0.
Resolving The Problem
Manually edit the ibm-web-ext.xml file to change the jdkSourceLevel parameter. For example:
jdkSourceLevel =15
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21691908