PI64139: DYNAMIC UPDATES TO JSP FILES ARE NOT PICKED UP.

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• After updating a JSP file within an ear or war file
  attempting to access that JSP via a browser reveals the
  unchanged original.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V9.0                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: After updating a JSP file within an     *
  *                      ear or war file attempting to access    *
  *                      that JSP via a browser reveals the      *
  *                      unchanged original.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After updating a JavaServer Pages (JSP) file within an ear or
  war file, the resulting Servlet class is re-generated with the
  same name and classloader. Since normal Servlets may require
  injection, Contexts and Dependency Injection (CDI) is used to
  construct them. The CDI code may have cached the Servlet
  instance and may not observe the fact that the class has in
  fact changed. The old cached copy is returned from CDI instead
  of creating a new instance.
  

Problem conclusion

• The Servlets generated from JSPs are now correctly
  re-constructed when requested by the Servlet container.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.1.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R900 PSY

     UP