PI97045: INVALID CONTENT-TYPE HEADER LOGS ARRAYINDEXOUTOFBOUNDSEXCEPTION.

8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
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
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• We handle the malformed Content-Type correctly,
  however, we are logging the original
  ArrayIndexOutOfBoundsException.
  

Local fix

• A temporary workaround would be to disable tracing for the
  MediaTypeHeaderDelegate class by adding the following trace
  string:
  
  org.apache.wink.common.internal.providers.header.MediaTypeHeader
  Delegate
  =off
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: JAX-RS 1.1 requests with invalid        *
  *                      Content-Type logs                       *
  *                      ArrayIndexOutOfBoundsException.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  JAX-RS 1.1 requests with invalid
  Content-Type logs
  ArrayIndexOutOfBoundsException.
  

Problem conclusion

• We handle the ArrayIndexOutOfBoundsException so there is no
  need to log the exception. We removed the logging statement to
  prevent logs from getting flooded and to minimize CPU use from
  bad requests.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.14.  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

• R800 PSY

     UP

• R850 PSY

     UP

• R900 PSY

     UP