[
https://issues.apache.org/jira/browse/FLUME-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Lassiège updated FLUME-2313:
---------------------------------
Description:
Currently, if the jms server is not available, the Flume jms source do not
start and never will.
We would like the source to be able to start even if the server is not
available and connect lately.
I'll try to provide a patch sooner.
was:
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 ?
Release Note: (was: Use of JNDI lookup to find destination. The default
mode still use "Create destination identifier" mode. Use
destinationLocator=JNDI to enable this feature)
> 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
> Labels: flume, jms, patch
>
> Currently, if the jms server is not available, the Flume jms source do not
> start and never will.
> We would like the source to be able to start even if the server is not
> available and connect lately.
> I'll try to provide a patch sooner.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
