Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3535

Documentation: Add note about connection close on commit() and rollback() to Deploy the WebSphere MQ Resource Adapter subchapter

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.0.0.CR2
    • 7.0.0.ER5
    • Documentation
    • None

      With WebSphere MQ 7.5 or WebSphereMQ 8 calling method commit() or rollback() on UserTransaction closes any JMS connections which was part of this transaction.
      As discribed in comment [1], adding tracking="false" to connection-definition element solves the problem.
      We need to document it. Could you please add it to subchapter "7.1. Deploy the WebSphere MQ Resource Adapter" to example of resource adapter configuration.

      Basicly, we need to replace 

              <connection-definition
                class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl"
                jndi-name="java:jboss/MQ.CONNECTIONFACTORY.NAME"
                pool-name="MQ.CONNECTIONFACTORY.NAME">

      with

              <connection-definition
                class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl"
                jndi-name="java:jboss/MQ.CONNECTIONFACTORY.NAME"
                pool-name="MQ.CONNECTIONFACTORY.NAME"
                tracking="false">

      Could you please add a note, that setting tracking="false", solves problem with WebSphere MQ 7.5 and 8, where method commit() or rollback() on UserTransaction closes any JMS connections which was part of this transaction. This part is related to documenting known limitation of WebSphere MQ in JBEAP-3142.

      [1] https://issues.jboss.org/browse/JBEAP-2844?focusedCommentId=13160393&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13160393

            rhn-support-pnag Priyanka Pandey
            mstyk_jira Martin Styk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: