IBM Support

IT22065: JSON4J.jar and MQLight specific code is being incorrectly shipped

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.


APAR status

  • Closed as program error.

Error description

  • The file shipped with MQ V9.0.0.2
    contains the following entry in its MANIFEST.MF file:
    Class-Path: jms.jar fscontext.jar providerutil.jar JSON4J.jar
    bcpkix-jdk15on-157.jar bcprov-jdk15on-157.jar
    This indicates that the JAR file JSON4J.jar is required by
    applications that use this JAR file. However, the JAR file is
    not shipped as part of the product. The JAR file is not
    required, and the entry in the MANIFEST.MF file is misleading.

Local fix

  • The reference to the JSON4J.jar file on the class-path should
    not be an issue for the customer and their use of the file for access to the MQ classes for
    JMS or MQ classes for Java APIs.

Problem summary

  • ****************************************************************
    This issue affects the users of the following product releases:
    - IBM MQ v8
    - IBM MQ v9
    Who have MQ classes for Java and/or classes for JMS applications
    that use:
    -  The JAR file
    -  Or the self-extracting JAR file
    <V.R.M.F>-WS-MQ-Install-Java-All.jar file
    Platforms affected:
    This APAR addresses 3 issues that were introduced as a result of
    the support for MQ Light:
    Issue 1:
    With the release of MQ v8.0.0.1,  JSON4J.jar was incorrectly
    added as a dependency to the classpath in the manifest file of
    Issue 2:
    With the release of MQ v8.0.0.1, JSON4J.jar was incorrectly
    packaged inside the Java-All.jar file.
    Issue 3:
    The package was being incorrectly
    packaged within

Problem conclusion

  • The following changes have been made to resolve these issues:
    Issue 1:
    The reference to JSON4J.jar have been removed from the classpath
    statement within the manifest file for the JAR.
    Issue 2:
    JSON4J.jar file has been removed from the
    <V.R.M.F>-WS-MQ-Install-Java-All.jar JAR file.  Applications
    that require the JSON4J library must obtain it from an
    alternative source after this APAR such as via the WebSphere
    Application Server runtime environment.
    Issue 3:
    The package is no longer included
    inside the JAR file.
    The fix is targeted for delivery in the following PTFs:
    Version    Maintenance Level
    v9.0 LTS
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name


  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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


  • Fixed component ID


Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
23 March 2018