agent.sources = s1 agent.channels = c1 agent.sinks = k1 agent.sources.s1.type = jms agent.sources.s1.initialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory agent.sources.s1.connectionFactory = 'name of connection factory' agent.sources.s1.providerURL = tcp://jndi server agent.sources.s1.destinationName = name of the queue agent.sources.s1.destinationType = QUEUE agent.sources.s1.channels = c1 agent.sources.s1.userName = username agent.sources.s1.passwordFile= /location/to/password
agent.channels.c1.type = memory agent.channels.c1.capacity = 1000 agent.channels.c1.transactionCapacity = 100 agent.sinks.k1.type = hbase agent.sinks.k1.channel = c1 agent.sinks.k1.table = table agent.sinks.k1.columnFamily = col On Fri, Jan 17, 2014 at 2:13 PM, Jeff Lord <[email protected]> wrote: > If you post your config right from the start it will go a long way towards > getting you a helpful answer sooner. > What do you have for the auth properties? > > e.g. > > a1.sources.r1.userName = admin > a1.sources.r1.passwordFile = /pathtopasswordfile.txt > > > On Fri, Jan 17, 2014 at 8:45 AM, P lva <[email protected]> wrote: > >> It was a problem with classpath. I fixed it but can you tell me how to >> pass the password to the configuration ? >> >> I sure its a local text file but I get this error despite mentioning the >> location of the password file in the configuration. >> >> 14/01/17 10:43:18 ERROR node.AbstractConfigurationProvider: Source s1 has >> been removed due to an error during configuration >> 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:471) >> at >> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:744) >> Caused by: javax.naming.AuthenticationException: Not permitted: invalid >> name or password [Root exception is javax.jms.JMSSecurityException: invalid >> name or password] >> at >> com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:670) >> at >> com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:491) >> at javax.naming.InitialContext.lookup(InitialContext.java:411) >> at >> org.apache.flume.source.jms.JMSSource.doConfigure(JMSSource.java:219) >> ... 12 more >> Caused by: javax.jms.JMSSecurityException: invalid name or password >> at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:591) >> at >> com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1350) >> at >> com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:4185) >> at >> com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:36) >> at >> com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:200) >> at >> com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:253) >> at >> com.tibco.tibjms.TibjmsQueueConnectionFactory.createQueueConnection(TibjmsQueueConnectionFactory.java:87) >> at >> com.tibco.tibjms.naming.TibjmsContext$Messenger.request(TibjmsContext.java:325) >> at >> com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:657) >> ... 15 more >> >> >> Thanks >> Pruthvi >> >> >> On Thu, Jan 16, 2014 at 2:29 PM, Jeff Lord <[email protected]> wrote: >> >>> Your config and anymore logfile context you can provide will help get >>> you an answer. >>> >>> >>> On Thu, Jan 16, 2014 at 10:29 AM, P lva <[email protected]> wrote: >>> >>>> Hello everyone, >>>> >>>> I'm trying to configure a jms source in flume agent, but i get this >>>> error >>>> >>>> Could not create initial context >>>> com.tibco.tibjms.naming.TibjmsInitialContextFactory provider >>>> tcb://xxx.xxxx.xxx.xxxx:xxx >>>> >>>> I came across this https://issues.apache.org/jira/browse/FLUME-2095and I >>>> have my configuration similar to that. The only change being the >>>> provider. >>>> >>>> Does provider url always be local machine. I have my queue set up in a >>>> remote jms server. >>>> Can someone please give me an example of a remote provider URL. >>>> >>>> Thanks >>>> >>>> >>>> >>> >> >
