IBM Support

IT15286: IVT is not working with Wildfly 10

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

  • Customer install WMQ V8 on Wildfly 10, then try to test the
    installation using IVT, but failed.
    Because the change in Wildfly 10, some default configurations
    are not applicable any more. After making some changes, such as
    JNDI location used by the MDB which run as part of the IVT, it
    works again.
    This APAR will fix this issue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The MQ V8.0 Resource Adapter.
    - The MQ V9.0 Long Term Support Release (LTSR) Resource Adapter.
    
    who want to deploy the resource adapter into WildFly V10.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In order to use the MQ resource adapter within a JEE application
    server, users must first deploy and successfully run the
    resource adapter installation verification test application into
    the same application server. If the RA IVT application cannot be
    run successfully, then the resource adapter is not supported
    within that application server.
    
    There were two issues with the RA IVT that prevented it from
    working in WildFly V10:
    
    Issue 1:
    The RA IVT contained a file called WMQ_IVT_MDB.jar, which stored
    the message-driven bean (MDB) part of the test application. The
    META-INF folder inside this JAR file contained a file called
    "jboss.xml" which was the JBoss-specific deployment descriptor
    for the application. WildFly V10 was a newer version of JBoss,
    and expected the application's deployment descriptor to be in a
    file called "jboss-ejb3.xml".
    
    Issue 2:
    The RA IVT also contained a file called WMQ_IVT.war, which was
    the web-based front end for the installation test application.
    This file contained two files that specified the resource
    references used by the web-based front end to look up JMS
    resources defined inside the application server's JNDI
    repository - these files were:
    
    - WEB-INF\web.xml
    - WEB-INF\jboss-web.xml
    
    The jboss-web.xml file was the one used by WildFly V10, and the
    resource references contained within this file were incorrect.
    

Problem conclusion

  • The MQ V8 and V9 LTSR resource adapter installation verification
    test application has been updated so that:
    
    - The WMQ_IVT_MDB.jar file now contains the file:
    
        META-INF\jboss-ejb3.xml
    
    which is used by WildFly V10.
    - The file:
    
      WEB-INF\jboss-web.xml
    
    within the WMQ_IVT.war file now contains the correct resource
    references for WildFly V10.
    
    
    In addition to these changes, users will need to update the
    file:
    
      <WildFly_Home>\standalone\configuration\standalone-full.xml
    
    to include the following subsystem definition for the MQ
    resource adapter:
    
    <subsystem xmlns="urn:jboss:domain:resource-adapters:4.0">
      <resource-adapters>
        <resource-adapter id="wmq.jmsra">
          <archive>
            wmq.jmsra.rar
          </archive>
          <transaction-support>NoTransaction</transaction-support>
          <connection-definitions>
            <connection-definition
    class-name="com.ibm.mq.connector.outbound.ManagedConnectionFacto
    ryImpl" jndi-name="java:jboss/jms/ivt/IVTCF" enabled="true"
    use-java-context="true" pool-name="IVTCF">
            <config-property name="channel">
              SYSTEM.DEF.SVRCONN
            </config-property>
            <config-property name="hostName">
              localhost
            </config-property>
            <config-property name="transportType">
              CLIENT
            </config-property>
            <config-property name="queueManager">
              ExampleQM
            </config-property>
            <config-property name="port">
              1414
            </config-property>
          </connection-definition>
          <connection-definition
    class-name="com.ibm.mq.connector.outbound.ManagedConnectionFacto
    ryImpl" jndi-name="java:jboss/jms/ivt/JMS2CF" enabled="true"
    use-java-context="true" pool-name="JMS2CF">
            <config-property name="channel">
              SYSTEM.DEF.SVRCONN
            </config-property>
            <config-property name="hostName">
              localhost
            </config-property>
            <config-property name="transportType">
              CLIENT
            </config-property>
            <config-property name="queueManager">
              ExampleQM
            </config-property>
            <config-property name="port">
              1414
            </config-property>
          </connection-definition>
        </connection-definitions>
        <admin-objects>
          <admin-object
    class-name="com.ibm.mq.connector.outbound.MQQueueProxy"
    jndi-name="java:jboss/jms/ivt/IVTQueue" pool-name="IVTQueue">
            <config-property name="baseQueueName">
              TEST.QUEUE
            </config-property>
          </admin-object>
         </admin-objects>
        </resource-adapter>
      </resource-adapters>
    </subsystem>
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.6
    v9.0 CD    9.0.2
    v9.0 LTS   9.0.0.1
    
    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

    IT15286

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-15

  • Closed date

    2016-10-28

  • Last modified date

    2017-06-01

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

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

Document Information

Modified date:
01 June 2017