PI25869: INCORRECT PROCESSING OF CONFIGURATION ELEMENTS IN THE SERVER.XML CONFIGURATION FILE

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• The CWWKG0032W message is printed if an enumeration value is
  used with the wrong case in the server.xml configuration file.
  For example, the <logging traceFormat="advanced"> element
  produces a warning because "advanced" is used rather than
  "ADVANCED".  The expectation is that enumeration values should
  be matched case-insensitively.
  
  The duration attributes in the server.xml configuration file
  depend on the locale of the running server.  For example, the
  <applicationMonitor pollingRate="5e"> element will be
  interpreted to mean 5 seconds in the pt_BR locale, but it will
  be an error in other locales.  The expectation is that the
  server.xml configuration file should be portable.
  
  The schema file produced by the ws-schemagen.jar tool does not
  allow variables to be mixed with non-string content.  For
  example, the <httpEndpoint httpPort="90${myport}"> element does
  not validate because the "90${myport}" string is not a valid
  integer and is not wholly a variable reference.
  
  The validation and processing of custom multi-valued attributes
  is not consistent with single-valued attributes.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The processing of some configuration    *
  *                      elements in the server.xml              *
  *                      configuration file is incorrect         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The value of an enumeration attribute was being matched case-
  sensitively.
  The parsing of duration attributes relied on translated strings
  for the duration abbreivations, which in some cases varied
  depending on the locale of the server process.  This behavior
  was undocumented.
  The generated schema for non-string attributes required the
  value to either match the type or wholly be a variable
  reference.
  The validation and processing of custom multi-valued attributes
  is not consistent with single-valued attributes.
  

Problem conclusion

• The value of an enumeration attribute is now matched case-
  insensitively to the enumeration values, and if the case does
  not match, the value is replaced with the enumeration value of
  the correct case.
  The parsing of duration attributes no longer depends on the
  locale of the server process.  The documented English duration
  abbreviations should always be used, but for backwards
  compatibility, the undocumented abbreviations from all
  translated locales is now hard-coded in the product.  This list
  of undocumented abbreviations will not be expanded even if the
  product is later translated to new locales.
  The generated schema for non-string attributes not allows any
  value if it contains a variable reference.
  The validation and processing of custom multi-valued attributes
  is now consistent with single-valued attributes.
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.4.  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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP