PI42817: HTTP Channel prints FFDCs for MalformedMessageExceptions and Ill egalStateExceptions while parsing request message

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.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

• While parsing the request message the HTTP channel would
  create an FFDC for MalformedMessageExceptions and
  IllegalStateExceptions
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: While parsing the request, the HTTP     *
  *                      Channel could generate First Failure    *
  *                      Data Captures (FFDCs)                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  While the HTTP Channel is parsing the request it could encounter
  an com.ibm.wsspi.genericbnf.exception.MalformedMessageException
  or an java.lang.IllegalStateException. These exceptions will
  generate FFDCs which are not required. An example of the
  MalformedMessageException FFDC would be:
  
       1  ------Start of DE processing------ = [6/17/14
  5:48:55:469 EDT]
       2  Exception =
  com.ibm.wsspi.genericbnf.exception.MalformedMessageException
       3  Source = HttpInboundLink.handleNewInformation
       4  probeid = 2
       5  Stack Dump =
  com.ibm.wsspi.genericbnf.exception.MalformedMessageException:
  Invalid LF found in token
       6          at
  com.ibm.ws.genericbnf.internal.BNFHeadersImpl.findTokenLength(BN
  FHeadersImpl.java:3053)
       7          at
  com.ibm.ws.genericbnf.internal.BNFHeadersImpl.parseTokenExtract(
  BNFHeadersImpl.java:3463)
       8          at
  com.ibm.ws.genericbnf.internal.GenericMessageImpl.parseLine(Gene
  ricMessageImpl.java:189)
       9          at
  com.ibm.ws.genericbnf.internal.GenericMessageImpl.parseMessage(G
  enericMessageImpl.java:323)
  

Problem conclusion

• The HTTP Channel was modified to not generate FFDCs for a
  MalformedMessageException or IllegalStateException during the
  parsing of the request
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.7.  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