Re: Camel route stop consuming
The SEDA queues is purely in-memory, so if the server crashes etc then the messages is lost, that is expected. On Mon, Aug 5, 2013 at 10:34 PM, jaime.salvador jaime.salva...@gmail.com wrote: Hi, Nice to see a reply by you (I have a paper copy of Camel in Action, great book!) The delay(500) is for spam prevention, having to much mails sends in a second the server is considerd a spam and is blocked. My route work as a massive mail sender that load balance the work to 50 mails account, and to prevent spam I put the delay. I notice that the route stop workin with activemq and with seda, the only diference is that with SEDA, if I restart the server, all messages are lost!!! thanks -- View this message in context: http://camel.465427.n5.nabble.com/Camel-route-stop-consuming-tp5736611p5736801.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: Camel route stop consuming
Hi,
Can you check the status of envioMailProcessor?
It could be some thing wrong when sending the mail to user.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Saturday, August 3, 2013 at 4:53 AM, jaime.salvador wrote:
Thanks for you reply, this is my routes
String dd[] = { direct:mail01, direct:mail02 ... direct:mail50 };
from(activemq:mail?concurrentConsumers=15)
.delay( 500 )
.loadBalance( )
.roundRobin( )
.to(dd);
from( direct:mail01 )
.beanRef( envioMailProcessor01, processLoadbalancer )
.
.
.
The envioMailProcesorXX sends a mail to the user.
Using seda, only replace activemq:mail with seda:mail
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-route-stop-consuming-tp5736611p5736714.html
Sent from the Camel - Users mailing list archive at Nabble.com
(http://Nabble.com).
Re: Camel route stop consuming
Hi You are taking in too many messages than you can process. Its not a good idea to have 2000+ messages in memory sitting on seda queues waiting to be processed. And why do you use the delay (500) ? On Thu, Aug 1, 2013 at 4:01 AM, jaime.salvador jaime.salva...@gmail.com wrote: Hi, I have a big number of messages routed to a ActiveMQ queue. the route works fine at begining, but after some hours of work, Camel stop comsuming the messages from queue. I try to get out activemq and use SEDA and the same problema apears. I have the next message when I try to stop Camel: 2013-07-28 11:32:53,140 INFO [org.apache.camel.impl.DefaultShutdownStrategy] - Waiting as there are still 2262 inflight and pending exchanges to complete, timeout in 287 seconds. Any idea? Thanks a lot -- View this message in context: http://camel.465427.n5.nabble.com/Camel-route-stop-consuming-tp5736611.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: Camel route stop consuming
Hi, Nice to see a reply by you (I have a paper copy of Camel in Action, great book!) The delay(500) is for spam prevention, having to much mails sends in a second the server is considerd a spam and is blocked. My route work as a massive mail sender that load balance the work to 50 mails account, and to prevent spam I put the delay. I notice that the route stop workin with activemq and with seda, the only diference is that with SEDA, if I restart the server, all messages are lost!!! thanks -- View this message in context: http://camel.465427.n5.nabble.com/Camel-route-stop-consuming-tp5736611p5736801.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel route stop consuming
Thanks for you reply, this is my routes
String dd[] = { direct:mail01, direct:mail02 ... direct:mail50 };
from(activemq:mail?concurrentConsumers=15)
.delay( 500 )
.loadBalance( )
.roundRobin( )
.to(dd);
from( direct:mail01 )
.beanRef( envioMailProcessor01, processLoadbalancer )
.
.
.
The envioMailProcesorXXsends a mail to the user.
Using seda, only replace activemq:mail with seda:mail
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-route-stop-consuming-tp5736611p5736714.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel route stop consuming
Can you show us your camel route? I'm not sure if it related to the SEDA queue is full. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thursday, August 1, 2013 at 10:01 AM, jaime.salvador wrote: Hi, I have a big number of messages routed to a ActiveMQ queue. the route works fine at begining, but after some hours of work, Camel stop comsuming the messages from queue. I try to get out activemq and use SEDA and the same problema apears. I have the next message when I try to stop Camel: 2013-07-28 11:32:53,140 INFO [org.apache.camel.impl.DefaultShutdownStrategy] - Waiting as there are still 2262 inflight and pending exchanges to complete, timeout in 287 seconds. Any idea? Thanks a lot -- View this message in context: http://camel.465427.n5.nabble.com/Camel-route-stop-consuming-tp5736611.html Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
