QueueFull means that the BlockingQueue created by SEDA and using the class (
http://cupi2.uniandes.edu.co/~cupi2/sitio/images/recursos/javadoc/j2se/1.5.0/docs/api/java/util/concurrent/BlockingQueue.html)
has been filled with 1000 messages but  the consumer has not been able to
process (=consume) the messages. So, you can by example increase the size of
the queue or add additional consumers using the property :
concurrentConsumers

Regards,

Charles Moulliard

Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel - Karaf - ServiceMix Committer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Blog : http://cmoulliard.blogspot.com |  Twitter :
http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard


On Fri, Aug 27, 2010 at 8:37 AM, Claus Ibsen <claus.ib...@gmail.com> wrote:

> Hi
>
> You should really check the documentation for the seda component
> http://camel.apache.org/seda
>
>
> On Thu, Aug 26, 2010 at 9:45 PM, Mark Webb <elihusma...@gmail.com> wrote:
> > I am getting an error in ActiveMQ as I test my routes.  I am sending
> > messages at a rate of about 1 every 10ms.  I am getting the following
> > error:
> >
> > 2010-08-26 15:41:13,937 | ERROR | Failed delivery for exchangeId:
> > 767c7514-b6ae-49fb-805a-78b13a0425af. Exhausted after delivery
> > attempt: 1 caught: java.lang.IllegalStateException: Queue full |
> > org.apache.camel.processor.DefaultErrorHandler | Camel thread 0:
> > seda://xyzabc
> > java.lang.IllegalStateException: Queue full
> >        at java.util.AbstractQueue.add(AbstractQueue.java:71)
> >        at
> org.apache.camel.component.seda.SedaProducer.process(SedaProducer.java:96)
> >        at
> org.apache.camel.processor.SendProcessor$1.doInProducer(SendProcessor.java:97)
> >
> >
> > How can I increase the capacity of the queue(s) that Camel is using?
> >
> > Thanks
> >
>
>
>
> --
> 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
>

Reply via email to