PQ27626: MSG IMW0096E "REQUEST PARSING FAILED" IS LOGGED TO THE ICSS ERROR LOG WHEN IT DOESN'T ALWAYS SIGNIFY AN ERROR.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Message , MSG IMW0096E " Request Parsing Failed " is issued and
  logged in the ICSS error log when it doesn't always signify an
  error condition. This message basically states that a timeout
  occured and that the socket has been closed by the server which
  only reflects a timeout condition and NOT an error condition.
  The message text in the WebMasters Guide is misleading and the
  fact that the message is logged in the ICSS error log indicates
  that an internal error has occured when this is not the actual
  senerio...
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: When message MSGIMW0096E "Request       *
  *                      parsing failed" logged in error log     *
  *                      file, it did not always indicate a real *
  *                      error even though it should. This       *
  *                      message was also logged when a timeout  *
  *                      occurred or the request was stopped     *
  *                      before any data being sent in.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When logging the message "Request parsing failed" to the error
  log file, the code did not correctly test whether it is a real
  error. The message was issued when HTParseRequest() returns null
  and Keep_Alive is zero. However when an input timeout occurs or
  when a request has been stopped by client before any data can
  be sent in, these conditions also hold. But these are not real
  errors and should not be reported as "Request parsing failed".
  

Problem conclusion

• Webserver code will be changed to use new flag HTRequestHasData
  in t_private to indicate whether request contains data or not.
  "Request parsing failed" should only be logged when request
  contains data but for some reason the request could not be
  correctly parsed so null is returned from HTParseRequest().
  
  The following COMPID's are affected by these changes:
  
  5697B1400 ICSS for OS/390  Version 2 ( release 2 only )
  5697C5800 LDGW for OS/390  Version 4.6
  5697A37L0 LDGW for OS/2    Version 4.6
  5697A43L0 LDGW for Win/NT  Version 4.6
  5697A45L0 LDGW for Solaris Version 4.6
  5697A47L0 LDGW for HP-UX   Version 4.6
  5697A74L0 LDGW for AIX     Version 4.6
  5639D54L0 LDGW for Win/95  Version 4.6
  5697D4300 LDGW for OS/390  Version 5
  
  The code changes are stored in CMVC under defect PQ21241a.
  
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

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

  PQ21241

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

Modules/Macros

• IMWCACHE IMWFCGI  IMWGSKIP IMWHTTPD IMWJAVDL
  IMWJGIW  IMWOCFGT IMWOCGPR IMWOCGTL IMWOHTAP IMWOHTDM IMWOPICO
  IMWSCONT IMWSERVR IMWYWWEX IMWYWWFR IMWYWWUS
  

Fix information

• Fixed component name

  DGW/WAS OS/390

• Fixed component ID

  5697D4300

Applicable component levels

• R500 PSY UQ31859

     UP99/07/14 P F907

• R501 PSY UQ31860

     UP99/07/15 P F907

• R502 PSY UQ31861

     UP99/07/15 P F907

• R503 PSY UQ31862

     UP99/07/15 P F907

• R510 PSY UQ31863

     UP99/07/14 P F907

• R511 PSY UQ31864

     UP99/07/14 P F907

• R512 PSY UQ31865

     UP99/07/14 P F907

• R513 PSY UQ31866

     UP99/07/14 P F907

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.