Re: Message not getting delivered from FTP to Activemq
Hi, When transferring files from remote FTP if the connection gets hindered due to some reason then is there any way camel takes care of this thing? -- View this message in context: http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181p5737183.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Message not getting delivered from FTP to Activemq
Is there any restriction on the file size? It is not able to poll a file more than 200 M.B in size. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181p5736247.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Message not getting delivered from FTP to Activemq
Hi Take a look at the localWorkDirectory or streamDownload options as by default the file is loaded into memory. So you may run out of memory. And for big files you need to use these options instead. Read more on the ftp doc page at http://camel.apache.org/ftp2 On Thu, Jul 25, 2013 at 6:19 AM, life1style1 chakravarty.sou...@gmail.com wrote: Is there any restriction on the file size? It is not able to poll a file more than 200 M.B in size. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181p5736247.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Message not getting delivered from FTP to Activemq
Hi All,
I am absolutely new to Apache Camel framework.
I am trying to route a message from FTP to Activemq.
There are no exceptions but the message is not getting delivered in
ActiveMQ's queue.
I am using the following code :
CamelContext context = new DefaultCamelContext();
ConnectionFactory connectionFactory = new
ActiveMQConnectionFactory(tcp://localhost:61616);
context.addComponent(activeMQ,
JmsComponent.jmsComponentAutoAcknowledge(connectionFactory));
context.addRoutes(new RouteBuilder() {
public void configure() {
from(ftp://nbleigftp@someserver//somefiles/password=secret;).to(activeMQ:queue:EIGIN);
}
});
context.start();
Thread.sleep(1000);
context.stop();
System.out.println(Sent);
But when I am doing the opposite i.e routing the message from ActiveMq to
FTP its working fine.
I have used the following:
from(activeMQ:queue:EIGIN).to(ftp://myftpserver/myFILES/?password=secret;);
Please let me know what I am missing.
Thanks in advance.
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Message not getting delivered from FTP to Activemq
Hi
You only run the application for 1 second that is not a long time. Use
a higher sleep value to have the app run for a bit to give it a chance
to connect to the ftp server and start downloading the file(s).
On Wed, Jul 24, 2013 at 10:06 AM, life1style1
chakravarty.sou...@gmail.com wrote:
Hi All,
I am absolutely new to Apache Camel framework.
I am trying to route a message from FTP to Activemq.
There are no exceptions but the message is not getting delivered in
ActiveMQ's queue.
I am using the following code :
CamelContext context = new DefaultCamelContext();
ConnectionFactory connectionFactory = new
ActiveMQConnectionFactory(tcp://localhost:61616);
context.addComponent(activeMQ,
JmsComponent.jmsComponentAutoAcknowledge(connectionFactory));
context.addRoutes(new RouteBuilder() {
public void configure() {
from(ftp://nbleigftp@someserver//somefiles/password=secret;).to(activeMQ:queue:EIGIN);
}
});
context.start();
Thread.sleep(1000);
context.stop();
System.out.println(Sent);
But when I am doing the opposite i.e routing the message from ActiveMq to
FTP its working fine.
I have used the following:
from(activeMQ:queue:EIGIN).to(ftp://myftpserver/myFILES/?password=secret;);
Please let me know what I am missing.
Thanks in advance.
--
View this message in context:
http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Message not getting delivered from FTP to Activemq
Thank you so much Claus. It worked for me. Now the issue is that the same file is being polled continuously until the sleep value ends. Any configurations available to avoid this? -- View this message in context: http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181p5736185.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Message not getting delivered from FTP to Activemq
You can set delete=true to delete the file after you have processed the file in Camel. Though that would delete the file on the FTP Server. There is also options to move the file instead of deleting it etc. Or use a idempotent consumer in Camel so it will skip the same file etc. And some other options. Its more what you need to do. On Wed, Jul 24, 2013 at 10:54 AM, life1style1 chakravarty.sou...@gmail.com wrote: Thank you so much Claus. It worked for me. Now the issue is that the same file is being polled continuously until the sleep value ends. Any configurations available to avoid this? -- View this message in context: http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181p5736185.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
Re: Message not getting delivered from FTP to Activemq
Thanks a lot once again. I have used preMove=inprogressmove=.done to get rid of redundant polling. -- View this message in context: http://camel.465427.n5.nabble.com/Message-not-getting-delivered-from-FTP-to-Activemq-tp5736181p5736189.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: The semantics of getIn and getOut (was: message not getting delivered)
On Thu, Oct 7, 2010 at 3:51 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: As promised, here's my take [1] on the getIn()/getOut() confusion. In a few days, when the dust will settle I'll take what's relevant from the post, and the comments that will follow and update the wiki page. I hope that clarifies the issue better, Hadrian [1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html Hadrian this is a nice piece of writing you did. Love to see the improved documentation at Apache which should be the result of this. Remember to update the javadoc on Exchange as well. I would also suggest adding some link or info to the FAQ from the Getting Started guides somewhere, in case the end user starts playing with a Processor, and thus gets exposed to the Exchange and the question on the getIn and getOut methods. On Oct 4, 2010, at 3:58 PM, Mark Webb wrote: I agree. But when producing an out I think you need to call Exchange.setIn(Message). Seems like when you call Exchange.setOut(Message) you are setting up a request-reply scenario which is not what I wanted. On Mon, Oct 4, 2010 at 1:54 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Yeah, there is still a lot of confusion. Unfortunately that page is bollocks and I'll have to get it cleaned up. Mark, I think you did the right thing actually, in a processor one should *not* modify the in, but produce an out, if needed. It's time to get that clarified! My $0.02, Hadrian On Oct 4, 2010, at 10:01 AM, Claus Ibsen wrote: On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb elihusma...@gmail.com wrote: Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. You are not the only one. See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: The semantics of getIn and getOut (was: message not getting delivered)
Thanks Claus, will do. I think there's a lot to do to improve documentation and I want to make that one of my priorities. I hope the whole community will join :). Cheers, Hadrian On Oct 8, 2010, at 12:10 PM, Claus Ibsen wrote: On Thu, Oct 7, 2010 at 3:51 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: As promised, here's my take [1] on the getIn()/getOut() confusion. In a few days, when the dust will settle I'll take what's relevant from the post, and the comments that will follow and update the wiki page. I hope that clarifies the issue better, Hadrian [1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html Hadrian this is a nice piece of writing you did. Love to see the improved documentation at Apache which should be the result of this. Remember to update the javadoc on Exchange as well. I would also suggest adding some link or info to the FAQ from the Getting Started guides somewhere, in case the end user starts playing with a Processor, and thus gets exposed to the Exchange and the question on the getIn and getOut methods. On Oct 4, 2010, at 3:58 PM, Mark Webb wrote: I agree. But when producing an out I think you need to call Exchange.setIn(Message). Seems like when you call Exchange.setOut(Message) you are setting up a request-reply scenario which is not what I wanted. On Mon, Oct 4, 2010 at 1:54 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Yeah, there is still a lot of confusion. Unfortunately that page is bollocks and I'll have to get it cleaned up. Mark, I think you did the right thing actually, in a processor one should *not* modify the in, but produce an out, if needed. It's time to get that clarified! My $0.02, Hadrian On Oct 4, 2010, at 10:01 AM, Claus Ibsen wrote: On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb elihusma...@gmail.com wrote: Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. You are not the only one. See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: The semantics of getIn and getOut (was: message not getting delivered)
As promised, here's my take [1] on the getIn()/getOut() confusion. In a few days, when the dust will settle I'll take what's relevant from the post, and the comments that will follow and update the wiki page. I hope that clarifies the issue better, Hadrian [1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html On Oct 4, 2010, at 3:58 PM, Mark Webb wrote: I agree. But when producing an out I think you need to call Exchange.setIn(Message). Seems like when you call Exchange.setOut(Message) you are setting up a request-reply scenario which is not what I wanted. On Mon, Oct 4, 2010 at 1:54 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Yeah, there is still a lot of confusion. Unfortunately that page is bollocks and I'll have to get it cleaned up. Mark, I think you did the right thing actually, in a processor one should *not* modify the in, but produce an out, if needed. It's time to get that clarified! My $0.02, Hadrian On Oct 4, 2010, at 10:01 AM, Claus Ibsen wrote: On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb elihusma...@gmail.com wrote: Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. You are not the only one. See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: message not getting delivered
Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: message not getting delivered
On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb elihusma...@gmail.com wrote: Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. You are not the only one. See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: message not getting delivered
Yeah, there is still a lot of confusion. Unfortunately that page is bollocks and I'll have to get it cleaned up. Mark, I think you did the right thing actually, in a processor one should *not* modify the in, but produce an out, if needed. It's time to get that clarified! My $0.02, Hadrian On Oct 4, 2010, at 10:01 AM, Claus Ibsen wrote: On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb elihusma...@gmail.com wrote: Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. You are not the only one. See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: message not getting delivered
I agree. But when producing an out I think you need to call Exchange.setIn(Message). Seems like when you call Exchange.setOut(Message) you are setting up a request-reply scenario which is not what I wanted. On Mon, Oct 4, 2010 at 1:54 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Yeah, there is still a lot of confusion. Unfortunately that page is bollocks and I'll have to get it cleaned up. Mark, I think you did the right thing actually, in a processor one should *not* modify the in, but produce an out, if needed. It's time to get that clarified! My $0.02, Hadrian On Oct 4, 2010, at 10:01 AM, Claus Ibsen wrote: On Mon, Oct 4, 2010 at 3:57 PM, Mark Webb elihusma...@gmail.com wrote: Thanks. I have things working now. It seems weird to me though that if in a Processor I take a message in, transform it into a newly created Message object that I should call Exchange.setIn(Message) instead of Exchange.setOut(Message). I think of a Processor as taking in a message and then sending it out, but it looks like that is not the case. Just need to adjust the way I think about things. You are not the only one. See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Sat, Oct 2, 2010 at 3:06 AM, Claus Ibsen claus.ib...@gmail.com wrote: See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
Re: message not getting delivered
See this FAQ http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html On Fri, Oct 1, 2010 at 10:37 PM, Mark Webb elihusma...@gmail.com wrote: I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
message not getting delivered
I am sending messages through a Camel route in ActiveMQ. My message reaches the end of the processing chain, and at the last processor I call exchange.setOut( newly created DefaultMessage ). When I look at the admin page for ActiveMQ, the topic shows that there is a message to be dequeued. It even says that there is a consumer connected to that topic, which is a GUI tool I wrote. The GUI tool makes a call to Consumer.setMessageListener. So why are the messages not making their way to my GUI tool? I am stumped as to why the messages sit in the topic and never leave if there is a listener for that topic. Of course the first thought is, is the Connection started? Yeah I verified that. In fact I can send messages to the topic via the web-based admin tool for ActiveMQ and the GUI receives them. Thanks for any help you have, Mark
