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

Heirarchical names for message destinations do not work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP 5.0.0
    • EAP 5.0.0.CR5
    • System
    • None
    • Release Notes
    • Hide

      There are 2 workarounds:

      1) The users can create the queue/topic through config files and not rely on the auto-creation. This infact is the best thing to do anyway.
      OR,
      2) Change the "destination" attribute (which actually represent the JNDI name of the destination) to be non-hierarchical. In the above example, change it from "queue/somequeue" to "somequeue"

      Show
      There are 2 workarounds: 1) The users can create the queue/topic through config files and not rely on the auto-creation. This infact is the best thing to do anyway. OR, 2) Change the "destination" attribute (which actually represent the JNDI name of the destination) to be non-hierarchical. In the above example, change it from "queue/somequeue" to "somequeue"

    Description

      This issue occurs only in cases where auto creation of destinations is enabled on the MDBs and the destination jndi-names are hierarchical

      The "destination" activation config property corresponds to the JNDI name of the destination http://www.jboss.org/file-access/default/members/jbossejb3/freezone/docs/tutorial/1.0.7/html/Message_Driven_Beans.html

      This was allowed and will continue to be allowed to have hierarchical names (see Tim's response to that JIRA here https://jira.jboss.org/jira/browse/JBMESSAGING-1667?focusedCommentId=12473722#action_12473722). Notice that in his example, he allows the use of hierarchical value for the JNDIName attribute whereas he says that hierarchical name should not be allowed as the "destinationName" which gets used for creating the MBean.

      So to accomodate the change in JBMESSAGING-1667 the additional thing that needs to be fixed is the http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_5_0/messaging/src/main/org/jboss/jms/server/destination/JBossMessagingCreateDestinationFactory.java which needs to be aware of this new rule. Right now, it's using the JNDI name of the destination (which is allowed to be hierarchical) as the destinationName while creating the MBean.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. JBAS-7694 Port JBPAPP-3026 to AS trunk

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jaikiran Jaikiran Pai (Inactive)
              rrajasek@redhat.com Rajesh Rajasekaran
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: