IBM Support

The SystemOut log does not show the jdkSourceLevel value when the default value has been changed

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

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"JSP","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21691908

Page Feedback