PI16432: RESTCONNECTOR ERROR "ARGUMENT TYPE MISMATCH" WHEN USING COMPOSITEDATA WITH BYTE []

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
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

• When using JMX  with the Liberty REST Connector, the following
  exception occurs:
  
  java.io.InvalidObjectException: argument type mismatch
  
  The problem occurs when a MBean CompositeData contains a Byte
  Array.
  The issue is with the JSONConverter utility that the JMX REST
  connector uses, related to how it processes a CompositeData
  having a byte[] inside of it.
  

Local fix

• N.A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The JMX REST connector was improperly   *
  *                      handling CompositeData objects that     *
  *                      contained a byte array.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During the conversion routine of a CompositeData object that
  contained a byte array the JMX REST connector was not setting
  the appropriate internal properties of the object, which
  resulted in an InvalidObjectException when a
  JMX.newMXBeanProxy was used.
  

Problem conclusion

• The CompositeData conversions are now properly handled for all
  types.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.3. 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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP