Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6303

Add JNDIURL attribute to the Resource Adapter

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Obsolete
    • Major
    • TBD EAP 5
    • EAP 5.1.0 Post Release
    • HornetQ
    • None
    • JBoss EAP 5.1.1, HornetQ .2.2.2 GA

    • Hide
      When a HornetQ queue was hosted on a remote HornetQ broker, and was not defined on the local instance of the HornetQ broker, HornetQ activation was ignoring multiple forward-slash characters in JNDI queue paths. If a queue was specified as <queue name="jms/queue/myQueue">, HornetQ was interpreting this as <queue name="myQueue">. An MDB listening on a remote queue was unable to connect to the queue because the forward-slashes were removed from the queue name. This issue is now fixed as part of this release.
      Show
      When a HornetQ queue was hosted on a remote HornetQ broker, and was not defined on the local instance of the HornetQ broker, HornetQ activation was ignoring multiple forward-slash characters in JNDI queue paths. If a queue was specified as <queue name="jms/queue/myQueue">, HornetQ was interpreting this as <queue name="myQueue">. An MDB listening on a remote queue was unable to connect to the queue because the forward-slashes were removed from the queue name. This issue is now fixed as part of this release.
    • Documented as Resolved Issue
    • ASSIGNED

    Description

      MDB listening on a remote queue is unable to connect to it if the queue name contains "/" character. For example

      <queue name="something here/queue name">
      <entry name="/something here/queue name"/>
      </queue>

      This happens if the queue is hosted by a remote HornetQ broker and is not defined on the local instance of HornetQ broker.

      This is caused by the fact that the HornetQ activation works on assumption that the last part of the queue JNDI name (part after the last "/" character) and the queue internal real name are the same. Though this assumption is probably correct in most of the cases it cannot be said that it would correct under all circumstances. It would fail if the internal queue name contains "/" character. for example:

      <queue name="jms/queue/myQueue">
      <entry name="/jms/queue/myQueue"/>
      </queue>
      In the above case horentq assumes that the queue name is myQueue where as in reality the name is "jms/queue/myQueue".
      It is also possible for the JNDI name and the queue name to be completely different. For example

      <queue name="jms/queue/mail/postbox">
      <entry name="/com/redhat/mailQueue"/>
      </queue>

      Attachments

        Issue Links

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-toross Tom Ross
              Jared Morgan Jared Morgan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: