Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-2816

JMS over WebsphereMQ doesn't support 'CLIENT' connections

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.2
    • 1.3
    • kernel
    • None
    • Tomcat 6, WindowsXP, WebsphereMQ 6.0

    Description

      Currently Axis2 can only connect withthe factory.createConnection() method from the JMS API.
      This is insufficient for WebspherMQ CLIENT connections, where the administrator must nominate a particular userID and password per connectionfactory, resulting in the following call which is unsupported in the Axis2 JMS code:
      factory.createConnection(userID, password)

      The attached Axis2 JMS files contain the fix to allow the deployer to specify a nominated userID and password through the standard Axis2 JNDI lookup mechanism.

      Attachments

        1. Axis2-websphereMQ-fix.zip
          10 kB
          Mark Badorrek
        2. WebsphereMQ-fix-29-06-2007.zip
          13 kB
          Mark Badorrek

        Activity

          People

            asankha Asankha Chamath Perera
            mbadorrek@avoga.com.au Mark Badorrek
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: