IBM Support

IT33764: IVT run on Wildfly-20 ignored DestinationLookup and ConnectionFactoryLookup activation properties

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

  • Installation Verification Test (IVT) run on Wildfly-20 ignored
    DestinationLookup and ConnectionFactoryLookup activation
    properties as they were not complying to JMS 2.0 Specification .
    
    According to JMS 2.0 Specification, MDB activation properties
    section the DestinationLookup and ConnectionFactoryLookup
    activation properties should begin with a lower case, as
    destinationLookup and connectionFactoryLookup respectively.
    
    When IBM MQ  IVT was deployed on WildFly-20 with IBM MQ resource
    adapter, WildFly-20 ignored DestinationLookup and
    ConnectionFactoryLookup activation properties.
    These invalid JMS property names in the ejb-jar.xml of IVT
    application, prevent the resource adapter IVT from working in
    WildFly-20
    
    Following messages were observed in the server.log:
    02:51:28,811 WARN  [org.jboss.as.ejb3] (MSC service thread 1-8)
    WFLYEJB0006: ActivationConfigProperty DestinationLookup will be
    ignored since it is not allowed by resource adapter: wmq.jmsra
    02:51:28,812 WARN  [org.jboss.as.ejb3] (MSC service thread 1-8)
    WFLYEJB0006: ActivationConfigProperty ConnectionFactoryLookup
    will be ignored since it is not allowed by resource adapter:
    wmq.jmsra
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users using the provided Installation Verification Test (IVT) to
    test the IBM MQ Resource Adapter
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Installation Verification Test (IVT) run on Wildfly-20 ignored
    DestinationLookup and ConnectionFactoryLookup activation
    properties as they were not complying with the JMS 2.0
    Specification .
    
    According to the JMS 2.0 Specification, the MDB activation
    properties section DestinationLookup and ConnectionFactoryLookup
    should begin with lower case, as destinationLookup and
    connectionFactoryLookup respectively.
    
    When the IBM MQ Resource Adapter IVT application was deployed on
    WildFly-20 with IBM MQ resource adapter, WildFly-20 ignored the
    DestinationLookup and ConnectionFactoryLookup activation
    properties. These invalid JMS property names in the ejb-jar.xml
    of the IVT application, resulted in the resource adapter IVT not
    initializing in WildFly-20
    
    These messages were observed in the server.log on attempted
    application startup:
    
    02:51:28,811 WARN  [org.jboss.as.ejb3] (MSC service thread 1-8)
    WFLYEJB0006: ActivationConfigProperty DestinationLookup will be
    ignored since it is not allowed by resource adapter: wmq.jmsra
    02:51:28,812 WARN  [org.jboss.as.ejb3] (MSC service thread 1-8)
    WFLYEJB0006: ActivationConfigProperty ConnectionFactoryLookup
    will be ignored since it is not allowed by resource adapter:
    wmq.jmsra
    

Problem conclusion

  • The DestinationLookup and ConnectionFactoryLookup activation
    properties have been updated to comply with the JMS 2.0
    specification as "destinationLookup" and
    "connectionFactoryLookup" respectively. The IBM MQ Resource
    Adapter installation verification test now runs correctly on all
    relevant application servers.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.11
    v9.2 LTS   9.2.0.5
    v9.x CD    9.2.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT33764

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-08-03

  • Closed date

    2021-11-17

  • Last modified date

    2021-11-17

  • 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

    IBM MQ BASE MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
18 November 2021