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/04 14:24:10 UTC

[jira] [Commented] (FLUME-924) Implement a JMS source for Flume NG

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

Hugo Lassiège commented on FLUME-924:
-------------------------------------

Hi,

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 ? I'm asking that because the configuration of Flume with a clusterised Weblogic server is not straightforward and I still can't get to make it work.

Regards,
Hugo  


> Implement a JMS source for Flume NG
> -----------------------------------
>
>                 Key: FLUME-924
>                 URL: https://issues.apache.org/jira/browse/FLUME-924
>             Project: Flume
>          Issue Type: New Feature
>    Affects Versions: v1.0.0
>            Reporter: Bruno Mahé
>            Assignee: Brock Noland
>             Fix For: v1.4.0
>
>         Attachments: FLUME-924-1.patch, FLUME-924-2.patch, FLUME-924-3.patch, FLUME-924-5.patch, FLUME-924-6.patch
>
>




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