PH62889: INSTRUMENT ADDITIONAL APACHE PROCESSING HOOKS FOR %{RH}E

APAR status

• Closed as new function.

Error description

• In 9.0, failures the "map_to_storage" phase are not reflected in
  %{RH}e logging.  It is likely %{RH}e will show the successful
  completion of the previous "translate_name" phase.
  
  
  192.168.1.1 - - [21/Aug/2024:12:33:36 -0500] "GET
  /app/resource HTTP/1.1" 500 538
  (mod_alias.c/0/translate_name)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM HTTP Server with %{RH}e in *
  *                  log format.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Logs with `%{RH}e` on a failing request *
  *                      sometimes report a module/callback that *
  *                      succeeded (did not return the final     *
  *                      error).                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Throughout the course of request processing, the core of Apache
  calls many different modules that have asked to be called back
  for specific named phases of processing.
  A serviceability feature in IHS tracks many of these and puts
  the final result in %{RH}e.  This tends to either capture the
  source of an error, or the handler that finally served the
  response (WAS Plugin, static files, etc).
  However, not all phases are instrumented this way. If a module
  running in an un-instrumented phase returns an error, %{RH}e
  will still have the successful result of some previous phase and
  (likely) different module.
  

Problem conclusion

• 9.0 was updated to instrument the map_to_storage phase, which
  should help cases where phases like "translate_name" were
  reported in %{RH}e.
  
  8.5 was additionally updated to instrument the fixups phase
  (already instrumented in 9.0)
  
  The fix for this APAR is targeted for inclusion in IBM HTTP
  Server fix packs 8.5.5.27 and 9.0.5.22. For more information,
  see 'Recommended Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  IBM HTTP SERVER

• Fixed component ID

  5724J0801

Applicable component levels