You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2014/02/04 18:44:12 UTC

[jira] [Commented] (FLUME-2311) Use standard way of finding queue/topic

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

Brock Noland commented on FLUME-2311:
-------------------------------------

[~hlassiege], would you be in a position to make the change and see if it fixes your issues?

> Use standard way of finding queue/topic
> ---------------------------------------
>
>                 Key: FLUME-2311
>                 URL: https://issues.apache.org/jira/browse/FLUME-2311
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Brock Noland
>
> 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)