You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Greg Mabrito (JIRA)" <ji...@apache.org> on 2013/09/17 23:11:56 UTC
[jira] [Commented] (FLUME-2095) JMS source with TIBCO
[ https://issues.apache.org/jira/browse/FLUME-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769968#comment-13769968 ]
Greg Mabrito commented on FLUME-2095:
-------------------------------------
The above works great for TIBCO EMS that doesn't utilize authN or authZ. However, we must authenticate in our Test environments. I am unsure on how to pass in the JNDI username/password and EMS username/password combinations. I have tried several combinations in the parameter file without success. Has anyone gotten this to work too?
> JMS source with TIBCO
> ---------------------
>
> Key: FLUME-2095
> URL: https://issues.apache.org/jira/browse/FLUME-2095
> Project: Flume
> Issue Type: Question
> Components: Sinks+Sources
> Affects Versions: v1.3.1
> Environment: Windows 7
> Reporter: Bhaskar Reddy
> Priority: Critical
>
> Hi,
> I was trying to use the JMS source to work with TIBCO, but I am encountering the exception below,
> org.apache.flume.FlumeException: Could not lookup ConnectionFactory
> at org.apache.flume.source.jms.JMSSource.doConfigure(JMSSource.java:222)
> at org.apache.flume.source.BasicSourceSemantics.configure(BasicSourceSemantics.java:65)
> at org.apache.flume.conf.Configurables.configure(Configurables.java:41)
> at org.apache.flume.node.AbstractConfigurationProvider.loadSources(AbstractConfigurationProvider.java:331)
> at org.apache.flume.node.AbstractConfigurationProvider.getConfiguration(AbstractConfigurationProvider.java:102)
> at org.apache.flume.node.PollingPropertiesFileConfigurationProvider$FileWatcherRunnable.run(PollingPropertiesFileConfigurationProvider.java:140)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.naming.NameNotFoundException: Name not found: 'com.tibco.tibjms.TibjmsQueueConnectionFactory'
> at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:715)
> at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:491)
> at javax.naming.InitialContext.lookup(InitialContext.java:392)
> at org.apache.flume.source.jms.JMSSource.doConfigure(JMSSource.java:219)
> ... 14 more
> Please find my configuration below,
> a1.sources.r1.type = jms
> a1.sources.r1.channels = c1
> a1.sources.r1.initialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
> a1.sources.r1.connectionFactory = com.tibco.tibjms.TibjmsQueueConnectionFactory
> a1.sources.r1.providerURL = tibjmsnaming://localhost:7222
> a1.sources.r1.destinationName = sample
> a1.sources.r1.destinationType = QUEUE
> I tried changing the configuration below,
> a1.sources.r1.type = jms
> a1.sources.r1.channels = c1
> a1.sources.r1.initialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
> a1.sources.r1.providerURL = tcp://localhost:7222
> a1.sources.r1.destinationName = sample
> a1.sources.r1.destinationType = QUEUE
> Thanks,
> Bhaskar.
--
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