[
https://issues.apache.org/jira/browse/FLUME-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655172#comment-13655172
]
Hari Shreedharan commented on FLUME-2043:
-----------------------------------------
Looks like this is an issue caused by the fact the we usually name our classes
ABCSourceConfigurationConstants - which is not the case in JMSSource, where
this class actually exists.
I will run the tests, try running the JMS source and then commit.
> JMS Source removed on failure to create configuration
> -----------------------------------------------------
>
> Key: FLUME-2043
> URL: https://issues.apache.org/jira/browse/FLUME-2043
> Project: Flume
> Issue Type: Bug
> Components: Configuration
> Affects Versions: v1.4.0
> Reporter: Deepesh Khandelwal
> Attachments: FLUME-2043.patch
>
>
> JMS Source used in agent configuration gets removed on running the agent.
> {code}
> 13/05/11 04:13:17 WARN conf.FlumeConfiguration: Removed jms-source due to
> Could not create configuration!
> {code}
> The configuration used is:
> {code}
> agent.sources = jms-source
> agent.channels = memoryChannel
> agent.channels.memoryChannel.type = memory
> agent.sources.jms-source.type = jms
> agent.sources.jms-source.channels = memoryChannel
> agent.sources.jms-source.initialContextFactory =
> org.apache.activemq.jndi.ActiveMQInitialContextFactory
> agent.sources.jms-source.providerURL = tcp://localhost:61616
> agent.sources.jms-source.destinationName = test
> agent.sources.jms-source.destinationType = queue
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
