IBM Support

IT28129: IBM MQ Resource Adapter ignores the configured temporary model queue in a WebSphere JNDI defined connection factory

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

  • An IBM MQ JMS Connection Factory is defined in the WebSphere
    Application Server V9.0 Java Naming and Directory Interface
    (JNDI) repository with a non-default temporary model queue,
    e.g., "MY.MODEL.QUEUE".  However, when a JMS Session or JMS
    Context is used to create a temporary queue, for example via the
    createTemporaryQueue() JMS API call, the queue manager's
    SYSTEM.DEFAULT.MODEL.QUEUE is used as the model queue for the
    temporary queue being created.  If the user performing this
    action is not authorized to access the
    SYSTEM.DEFAULT.MODEL.QUEUE, then the request to create the
    temporary queue would fail with the exception:
      JMSWMQ2008: Failed to open MQ queue
    with the linked MQ reason code MQRC_NOT_AUTHORIZED (2035).

Local fix

Problem summary

  • ****************************************************************
    This issue affects users of the IBM MQ Resource Adapter within
    WebSphere Application Server (WSAS) V9.0 who persist JMS
    Connection Factories definitions to the WSAS JNDI repository
    that are configured with a non-default temporary model queue.
    This also affects users of the IBM MQ classes for JMS who
    programmatically create an MQ JMS Connection Factory and
    configure the temporary model queue on it using the method:
      setStringProperty(String, String)
    passing in "TM" as the first argument.
    Platforms affected:
    An issue existed in the MQ classes for JMS Connection Factory
    validation code such that it expected the short name for the
    temporary model queue configuration option to be "Tm"
    (lower-case 'm').  This was incorrect as the short name is "TM"
    (upper-case 'M').  The result of this was that when the MQ JMS
    Connection Factory was being created from a JNDI persisted
    definition in WebSphere Application Server, the temporary model
    queue configuration option, "TM", was deemed invalid and
    ignored.  As such, the defined temporary model queue on the JMS
    Connection Factory object used by the application was not
    updated and remained the default value,

Problem conclusion

  • The IBM MQ classes for JMS Connection Factory validation code
    has been corrected to expect "TM" as the short JNDI
    administration name for the temporary model queue configuration
    The fix is targeted for delivery in the following PTFs:
    Version    Maintenance Level
    v9.0 LTS
    v9.1 CD    9.1.3
    v9.1 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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 February 2019