PH06565: <MULTI-CONFIG> CHILD ELEMENTS ARE ADDED TO WEB.XML/WEB-MERGED.XML

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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16

APAR status

• Closed as program error.

Error description

• If the application's web.xml file contains an empty
  <multipart-config> element as follows:
  
  <multipart-config>
  </multipart-config>
  
  The child elements <max-file-size>, <max-request-size>, and
  <file-size-threshold> are added to the web.xml/web-merged.xml
  file after the application deployment as follows:
  
  <multipart-config>
     <max-file-size>0</max-file-size>
     <max-request-size>0</max-request-size>
     <file-size-threshold>0</file-size-threshold>
  </multipart-config>
  
  The child elements should not be added automatically when the
  application is being deployed.
  

Local fix

• Remove the child elements in the web.xml/web-merged.xml after
  the application is deployed.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server with web applications containing an  *
  *                  empty <multipart-config> element in         *
  *                  web.xml.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: If web.xml contains an empty            *
  *                      <multipart-config> element,             *
  *                      child elements are added with default   *
  *                      values during deployment.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the application's web.xml file contains an empty
  <multipart-config> element as follows:
  <multipart-config>
  </multipart-config>
  The child elements <max-file-size>, <max-request-size>, and
  <file-size-threshold> are added to the web.xml/web-merged.xml
  file after the application deployment as follows:
  <multipart-config>
  <max-file-size>0</max-file-size>
  <max-request-size>0</max-request-size>
  <file-size-threshold>0</file-size-threshold>
  </multipart-config>
  The default value of zero for max-file-size is not consistent
  with the Java EE specification.  The default value should be
  -1, unlimited.
  The child elements should not be added automatically when the
  application is being deployed.
  

Problem conclusion

• The code has been updated so that unspecified child elements
  of the <multipart-config> element of a web.xml are not
  automatically added during deployment.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.16 and 9.0.0.11.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP