You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Hugo Lassiège (JIRA)" <ji...@apache.org> on 2014/02/06 14:50:09 UTC

[jira] [Created] (FLUME-2313) Start the source even if the JMS queue/topic is not available

Hugo Lassiège created FLUME-2313:
------------------------------------

             Summary: Start the source even if the JMS queue/topic is not available
                 Key: FLUME-2313
                 URL: https://issues.apache.org/jira/browse/FLUME-2313
             Project: Flume
          Issue Type: Bug
    Affects Versions: v1.4.0
            Reporter: Hugo Lassiège


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 ?




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)