Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-3298

Cannot create bridge to WebSphere queue using default messaging provider

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.4.2
    • Fix Version/s: 5.7.0
    • Component/s: Broker
    • Labels:
      None
    • Environment:

      all

      Description

      I am attempting to configure a queue-to-queue bridge from ActiveMQ to a queue in WebSphere 7. The WebShere queue used the internal 'default messaging provider'. The bridge configuration provides the JNDI name for the queue.

      In the ActiveMQ JmsQueueConnector.createForeignQueue method, the queue is created using:

      try

      { result = session.createQueue(queueName); }

      catch (JMSException e) {
      // look-up the Queue
      try {
      result = (Queue)jndiOutboundTemplate.lookup(queueName, Queue.class);
      ...

      Unfortunately, the Session.createQueue method in the WebSphere connector does not throw an exception at this point; instead a Queue object is created which cannot be used for message transmission. Ideally there would be a configuration option which bypasses the createQueue call and goes direct to the JNDI lookup.

      Or try the JNDI approach first and fallback to createQueue?

        Attachments

          Activity

            People

            • Assignee:
              tabish Timothy A. Bish
              Reporter:
              richard.evans@datanomic.com Richard Evans
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: