Fix (APAR): PK19526
Status: Fix
Release: 6.0.2.9, 6.0.2.7, 6.0.2.5, 6.0.2.3
Operating System: AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/400,Solaris,Windows
Supersedes Fixes:
CMVC Defect: PK19526
Byte size of APAR: 6014 (6.0.2.3, 6.0.2.5, 6.0.2.7); 6015 (6.0.2.9)
Date: 2006-05-16
Abstract: JSP compile fails, ignores EL-IGNORED in WEB.XML in V6.0.2.5
Description/symptom of problem:
PK19526 resolves the following problem:
ERROR DESCRIPTION:
See eclipse bugzilla defect 124492:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=124492
For compatibility with our customer's old JSP which use JSP 1.2
and JSTl 1.1, we inserted the following tags into 'web.xml' of
the application module 'Stores.war'. The tags were inserted
to disable EL:
*.jsp
true
In WAS 6.0.2 or earlier, no errors are seen.
In WAS 6.0.2.5, JSP compilation fails, for example:
***************************************************************
[2/9/06 14:08:20:038 IST] 0000002d WebApp E SRVE0026E:
[Servlet
Error]-[JSPG0227E: Exception caught while translating
/SampleJSTL10.jsp:
/SampleJSTL10.jsp(17,7) --> JSPG0124E: Custom tag attribute
items cannot
be runtime expression. value: "[${header}]"
]: com.ibm.ws.jsp.translator.JspTranslationException: JSPG0227E:
Exception caught while translating /SampleJSTL10.jsp:
/SampleJSTL10.jsp(17,7) --> JSPG0124E: Custom tag attribute
items cannot be runtime expression. value: "[${header}]"
***************************************************************
The compilation error occurs because the value of 'el-egnored'
that was added to web.xml is being ignored.
This error is seen in WebSphere Application Server versions
v6.0.2.3, V6.0.2.5, and V6.0.2.7. This error is not seen in
earlier version (V6.0.2.0 or V6.0.2.1). For example, placing
the wccm_base.jar from a V6.0.2.1 installation into a
V6.0.2.5 installation remediates the problem. (This is not
a recommended workaround.)
LOCAL FIX:
none
PROBLEM SUMMARY
USERS AFFECTED:
Users of WebSphere Application Server versions 6.0.2.3
through 6.0.2.10, on all available platforms.
Users with J2EE applications with JSPs may be affected.
PROBLEM DESCRIPTION:
JSP compile fails, ignores EL-IGNORED in WEB.XML in V6.0.2.5
RECOMMENDATION:
None
See eclipse bugzilla defect 124492:
bugs.eclipse.org/bugs/show_bug.cgi?id=124492
For compatibility with our customer's old JSP which use
JSP 1.2 and JSTl 1.1, we inserted the following tags into
'web.xml' of the application module 'Stores.war'. The tags
were inserted to disable EL:
*.jsp
true
In WAS 6.0.2.1 or earlier, no errors are seen.
In WAS 6.0.2.5, JSP compilation fails, for example:
*************************************************************
[2/9/06 14:08:20:038 IST] 0000002d WebApp E
SRVE0026E: [ServletError]-[JSPG0227E: Exception caught while
translating /SampleJSTL10.jsp:
/SampleJSTL10.jsp(17,7) --> JSPG0124E: Custom tag attribute
items cannot be runtime expression. value: "[${header}]"
]: com.ibm.ws.jsp.translator.JspTranslationException:
JSPG0227E: Exception caught while translating
/SampleJSTL10.jsp:
/SampleJSTL10.jsp(17,7) --> JSPG0124E: Custom tag attribute
items cannot be runtime expression. value: "[${header}]"
*************************************************************
The compilation error occurs because the value of 'el-egnored'
that was added to web.xml is being ignored.
PROBLEM CONCLUSION:
Received CORONA patch for 6.0.x levels.
Published two ifixes:
For 6.0.2.3, 6.0.2.5, and 6.0.2.7: "6.0.2.3-WS-WAS-IFPK19526"
For 6.0.2.9: "6.0.2.9-WS-WAS-IFPK19526"
The fix is included in the 6.0.2.11 service pack.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Directions to apply fix: NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note
Fix applies to Editions:
Release 6.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)
Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both
NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt.
The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991
For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400
1) Copy PKxxxxx.pak file directly to the maintenance directory
2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.
3) Launch Update Installer
4) Enter the installation location of the WebSphere product you want to update.
5) Select the "Install maintenance package" operation.
6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory).
7) Install the maintenance package.
8) Restart WebSphere
Directions to remove fix: NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX
Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.
1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.
2) Start Update Installer
3) Enter the installation location of the WebSphere product you want to remove the fix.
4) Select "Uninstall maintenance package" operation.
5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).
6) UnInstall maintenance package.
7) Restart WebSphere
Directions to re-apply fix: 1) Shutdown WebSphere.
2) Follow the Fix instructions to apply the fix.
3) Restart WebSphere.
Additional Information: IFix is for all distributed platforms, at levels
6.0.2.3, 6.0.2.5, 6.0.2.7, and 6.0.2.9.