[FLUME-2311] Use standard way of finding queue/topic

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Labels: flume jms patch
• Release Note: Use of JNDI lookup to find destination. The default mode still use "Create destination identifier" mode. Use destinationLocator=JNDI to enable this feature
• Assignee: Hugo Lassiège
• Reporter: Brock Noland
• Created: 04/Feb/14 17:42
• Updated: 28/Jun/18 12:37
• Resolved: 07/Feb/14 17:12

Description

Here https://issues.apache.org/jira/browse/FLUME-924?focusedCommentId=13890651&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13890651

hlassiege says:

I'm currently using this jms source to connect on Weblogic message bus. I'm wondering why the JMSMessageConsumer use createQueue and createTopic instead of lookup to find the destinations (line 83 to 90).
It seems that "createQueue" or "createTopic" are not the recommended way because it is not portable (I saw that warning in Weblogic documentation even if I can't justify this assertion).
The documentation recommends to use a JNDI lookup (http://docs.oracle.com/cd/E23943_01/web.1111/e13727/lookup.htm#BABDFCIC).
Is there any reason to use createQueue instead of lookup ?

Issue Links

• is related to: FLUME-2313 Start the source even if the JMS queue/topic is not available
• relates to: FLUME-3248 Missing 'destinationLocator' parameter in the documentation of JMS Source