You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by ariekenb <aa...@lmco.com> on 2009/05/06 16:36:47 UTC
SEDA Component Exception: No producer, this processor has not been
started!
I two beans named producer and consumer. Producer starts a java.util.Timer
in its init method to pop every 100 ms and send a message to a SEDA queue
(using a ProducerTemplate it got from @EndpointInject). Consumer has a
method to receive messages from the queue. Here's the camel route:
<camel:camelContext
id="test">
<camel:endpoint
id="sedaEndpoint"
uri="seda:test" />
<camel:route>
<camel:from
uri="sedaEndpoint" />
<camel:to
uri="bean:consumer?methodName=processMessage" />
</camel:route>
</camel:camelContext>
I find sometimes just after Producer sends its first message, I get this
error logged. This happens before Consumer has received any messages:
09:22:35,087 | ERROR | da:test thread:1 | DeadLetterChannel |
rg.apache.camel.processor.Logger 203 | Failed delivery for exchangeId:
ID-swim4/48409-1241619754977/0-0. On delivery attempt: 0 caught:
java.lang.IllegalStateException: No producer, this processor has not been
started!
java.lang.IllegalStateException: No producer, this processor has not been
started!
at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:78)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
at
org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:185)
at
org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:132)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52)
at org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:69)
at java.lang.Thread.run(Thread.java:619)
This doesn't seem to cause anything bad to happen. Even when this exception
happens, Consumer still receives all messages from Producer in order.
I'm just wondering why this happens. Is there a race condition during
startup so that Producer can get its endpoint injected before camel is ready
to route messages to Consumer? Should I be concerned about this?
--
View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23407604.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, May 23, 2009 at 4:14 PM, ariekenb <aa...@lmco.com> wrote:
>
> Hi Claus -
>
> Consumer.java: http://pastebin.com/f4d1425bf
> Producer.java: http://pastebin.com/fa83d285
> camel.xml: http://pastebin.com/f4d1425bf
>
>
> I am running this in an OSGi bundle in FUSE ESB 4. Running this inside FUSE
> ESB 4.0.0.4 (Camel 1.5.4.0-fuse) I am able to make the "No producer, this
> processor has not been started" exception happen just after my bundle is
> deployed. The exception does not happen every time, but it does occur
> frequently.
>
> I just tried upgrading to FUSE ESB 4.1.0.0 (Camel 1.6.0.0-fuse) and it seems
> I am no longer able to make the exception happen with this version so far.
> Looking at the release notes I am not certain which change would fix this
> problem, but I guess I am happy it seems to work reliably now. :)
Hi
Ah great yeah I think I know why. How the consumer is started in the
SEDA endpoint have been changed to better leverage the JDK Concurrent
API with its ExecutorService API.
You can see the code difference in the links below:
1.5.0:
https://svn.apache.org/repos/asf/camel/tags/camel-1.5.0/camel-core/src/main/java/org/apache/camel/component/seda/SedaConsumer.java
1.6.1 (aka FUSE MR 1.6.0):
https://svn.apache.org/repos/asf/camel/tags/camel-1.6.1/camel-core/src/main/java/org/apache/camel/component/seda/SedaConsumer.java
>
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> Can you post your route and POJO code to pastebin or create a JIRA
>> ticket in Camel then I can take a look at it.
>>
>> On Sat, May 16, 2009 at 1:54 PM, ariekenb <aa...@lmco.com>
>> wrote:
>>>
>>>
>>> Claus Ibsen-2 wrote:
>>>>
>>>>>
>>>>> Is there an easy way to know if all components/processors in a
>>>>> CamelContext
>>>>> are started? I can easily get the CamelContext injected into the
>>>>> producer
>>>>> bean, but I'm not sure what components I would need to check isStarted
>>>>> on
>>>>> before sending a message.
>>>> Yeah I guess you can check the camel context itself if its started.
>>>> There where some changes recently regarding this. Might work better in
>>>> 1.6.1+.
>>>> There is a JIRA Ticket somewhere on this. Dont have time to find it.
>>>>
>>> I think you're referring to this JIRA issue:
>>> http://issues.apache.org/activemq/browse/CAMEL-1509 If I understand
>>> correctly the meaning of "isStarted" on a camel context was fixed up so
>>> "isStarted" is false while "isStarting" is true.
>>>http://pastebin.com/f4d1425bf
>>> It seems strange to me that a spring-injected camel resource like
>>> ProducerTemplate can be "not started" when it is injected. Aren't
>>> injected
>>> resources supposed to be ready to go immediately?
>>>
>>> Does camel inject resources before the context is started for performance
>>> reasons? Are there any plans to change this?
>>> --
>>> View this message in context:
>>> http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23573062.html
>>> Sent from the Camel - Users (activemq) mailing list archive at
>>> Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>>
>
> --
> View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23684906.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by ariekenb <aa...@lmco.com>.
Hi Claus -
Consumer.java: http://pastebin.com/f4d1425bf
Producer.java: http://pastebin.com/fa83d285
camel.xml: http://pastebin.com/f4d1425bf
I am running this in an OSGi bundle in FUSE ESB 4. Running this inside FUSE
ESB 4.0.0.4 (Camel 1.5.4.0-fuse) I am able to make the "No producer, this
processor has not been started" exception happen just after my bundle is
deployed. The exception does not happen every time, but it does occur
frequently.
I just tried upgrading to FUSE ESB 4.1.0.0 (Camel 1.6.0.0-fuse) and it seems
I am no longer able to make the exception happen with this version so far.
Looking at the release notes I am not certain which change would fix this
problem, but I guess I am happy it seems to work reliably now. :)
Claus Ibsen-2 wrote:
>
> Hi
>
> Can you post your route and POJO code to pastebin or create a JIRA
> ticket in Camel then I can take a look at it.
>
> On Sat, May 16, 2009 at 1:54 PM, ariekenb <aa...@lmco.com>
> wrote:
>>
>>
>> Claus Ibsen-2 wrote:
>>>
>>>>
>>>> Is there an easy way to know if all components/processors in a
>>>> CamelContext
>>>> are started? I can easily get the CamelContext injected into the
>>>> producer
>>>> bean, but I'm not sure what components I would need to check isStarted
>>>> on
>>>> before sending a message.
>>> Yeah I guess you can check the camel context itself if its started.
>>> There where some changes recently regarding this. Might work better in
>>> 1.6.1+.
>>> There is a JIRA Ticket somewhere on this. Dont have time to find it.
>>>
>> I think you're referring to this JIRA issue:
>> http://issues.apache.org/activemq/browse/CAMEL-1509 If I understand
>> correctly the meaning of "isStarted" on a camel context was fixed up so
>> "isStarted" is false while "isStarting" is true.
>>http://pastebin.com/f4d1425bf
>> It seems strange to me that a spring-injected camel resource like
>> ProducerTemplate can be "not started" when it is injected. Aren't
>> injected
>> resources supposed to be ready to go immediately?
>>
>> Does camel inject resources before the context is started for performance
>> reasons? Are there any plans to change this?
>> --
>> View this message in context:
>> http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23573062.html
>> Sent from the Camel - Users (activemq) mailing list archive at
>> Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
--
View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23684906.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Can you post your route and POJO code to pastebin or create a JIRA
ticket in Camel then I can take a look at it.
On Sat, May 16, 2009 at 1:54 PM, ariekenb <aa...@lmco.com> wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>>>
>>> Is there an easy way to know if all components/processors in a
>>> CamelContext
>>> are started? I can easily get the CamelContext injected into the
>>> producer
>>> bean, but I'm not sure what components I would need to check isStarted on
>>> before sending a message.
>> Yeah I guess you can check the camel context itself if its started.
>> There where some changes recently regarding this. Might work better in
>> 1.6.1+.
>> There is a JIRA Ticket somewhere on this. Dont have time to find it.
>>
> I think you're referring to this JIRA issue:
> http://issues.apache.org/activemq/browse/CAMEL-1509 If I understand
> correctly the meaning of "isStarted" on a camel context was fixed up so
> "isStarted" is false while "isStarting" is true.
>
> It seems strange to me that a spring-injected camel resource like
> ProducerTemplate can be "not started" when it is injected. Aren't injected
> resources supposed to be ready to go immediately?
>
> Does camel inject resources before the context is started for performance
> reasons? Are there any plans to change this?
> --
> View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23573062.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by ariekenb <aa...@lmco.com>.
Claus Ibsen-2 wrote:
>
>>
>> Is there an easy way to know if all components/processors in a
>> CamelContext
>> are started? I can easily get the CamelContext injected into the
>> producer
>> bean, but I'm not sure what components I would need to check isStarted on
>> before sending a message.
> Yeah I guess you can check the camel context itself if its started.
> There where some changes recently regarding this. Might work better in
> 1.6.1+.
> There is a JIRA Ticket somewhere on this. Dont have time to find it.
>
I think you're referring to this JIRA issue:
http://issues.apache.org/activemq/browse/CAMEL-1509 If I understand
correctly the meaning of "isStarted" on a camel context was fixed up so
"isStarted" is false while "isStarting" is true.
It seems strange to me that a spring-injected camel resource like
ProducerTemplate can be "not started" when it is injected. Aren't injected
resources supposed to be ready to go immediately?
Does camel inject resources before the context is started for performance
reasons? Are there any plans to change this?
--
View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23573062.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, May 6, 2009 at 5:39 PM, ariekenb <aa...@lmco.com> wrote:
>
> Thanks Claus.
>
> I haven't done anything special to configure a DeadLetterChannel. I assume
> that means I get the default settings from here
> http://camel.apache.org/dead-letter-channel.html (try up to 5 times 1 second
> apart)?
Yes in Camel 1.x the DLC is the default error handler.
>
> Are messages guaranteed to stay in order if the first message goes into the
> DeadLetterChannel? I have observed the first message seems to always be
> delivered first even when the exception below happens.
Yeah as the SEDA consumer only have 1 consumer. Unless you add
concurrentConsumer=5 to the SEDA queue.
Requires Camel 1.6.1+
>
> Is there an easy way to know if all components/processors in a CamelContext
> are started? I can easily get the CamelContext injected into the producer
> bean, but I'm not sure what components I would need to check isStarted on
> before sending a message.
Yeah I guess you can check the camel context itself if its started.
There where some changes recently regarding this. Might work better in
1.6.1+.
There is a JIRA Ticket somewhere on this. Dont have time to find it.
Its dinner time. Take care and see you tomorrow.
>
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> Yeah its a race condition. You can configure your timer fire bean to
>> wait eg some longer before it fires the first message.
>>
>> As long as you use the DeadLetterChannel you should in fact not worry
>> as it does redeliveries so in the next attempt it will usually succeed
>> as the producer is started in the meantime. However if you disable
>> redelivery etc. then the first message will not be delivered and lost.
>>
>> But it would be best to wait a little before sending the very first
>> message.
>>
>> Otherwise you can use some Camel API to find the processor and test
>> whether it is started with: isStarted()
>>
>>
>> On Wed, May 6, 2009 at 4:36 PM, ariekenb <aa...@lmco.com>
>> wrote:
>>>
>>> I two beans named producer and consumer. Producer starts a
>>> java.util.Timer
>>> in its init method to pop every 100 ms and send a message to a SEDA queue
>>> (using a ProducerTemplate it got from @EndpointInject). Consumer has a
>>> method to receive messages from the queue. Here's the camel route:
>>>
>>> <camel:camelContext
>>> id="test">
>>>
>>> <camel:endpoint
>>> id="sedaEndpoint"
>>> uri="seda:test" />
>>>
>>> <camel:route>
>>> <camel:from
>>> uri="sedaEndpoint" />
>>> <camel:to
>>>
>>> uri="bean:consumer?methodName=processMessage" />
>>> </camel:route>
>>>
>>> </camel:camelContext>
>>>
>>>
>>> I find sometimes just after Producer sends its first message, I get this
>>> error logged. This happens before Consumer has received any messages:
>>>
>>> 09:22:35,087 | ERROR | da:test thread:1 | DeadLetterChannel
>>> |
>>> rg.apache.camel.processor.Logger 203 | Failed delivery for exchangeId:
>>> ID-swim4/48409-1241619754977/0-0. On delivery attempt: 0 caught:
>>> java.lang.IllegalStateException: No producer, this processor has not been
>>> started!
>>> java.lang.IllegalStateException: No producer, this processor has not been
>>> started!
>>> at
>>> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:78)
>>> at
>>> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
>>> at
>>> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:185)
>>> at
>>> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:132)
>>> at
>>> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
>>> at
>>> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52)
>>> at
>>> org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:69)
>>> at java.lang.Thread.run(Thread.java:619)
>>>
>>>
>>> This doesn't seem to cause anything bad to happen. Even when this
>>> exception
>>> happens, Consumer still receives all messages from Producer in order.
>>>
>>> I'm just wondering why this happens. Is there a race condition during
>>> startup so that Producer can get its endpoint injected before camel is
>>> ready
>>> to route messages to Consumer? Should I be concerned about this?
>>> --
>>> View this message in context:
>>> http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23407604.html
>>> Sent from the Camel - Users (activemq) mailing list archive at
>>> Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>> Apache Camel Reference Card:
>> http://refcardz.dzone.com/refcardz/enterprise-integration
>> Interview with me:
>> http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
>>
>>
>
> --
> View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23409362.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by ariekenb <aa...@lmco.com>.
Thanks Claus.
I haven't done anything special to configure a DeadLetterChannel. I assume
that means I get the default settings from here
http://camel.apache.org/dead-letter-channel.html (try up to 5 times 1 second
apart)?
Are messages guaranteed to stay in order if the first message goes into the
DeadLetterChannel? I have observed the first message seems to always be
delivered first even when the exception below happens.
Is there an easy way to know if all components/processors in a CamelContext
are started? I can easily get the CamelContext injected into the producer
bean, but I'm not sure what components I would need to check isStarted on
before sending a message.
Claus Ibsen-2 wrote:
>
> Hi
>
> Yeah its a race condition. You can configure your timer fire bean to
> wait eg some longer before it fires the first message.
>
> As long as you use the DeadLetterChannel you should in fact not worry
> as it does redeliveries so in the next attempt it will usually succeed
> as the producer is started in the meantime. However if you disable
> redelivery etc. then the first message will not be delivered and lost.
>
> But it would be best to wait a little before sending the very first
> message.
>
> Otherwise you can use some Camel API to find the processor and test
> whether it is started with: isStarted()
>
>
> On Wed, May 6, 2009 at 4:36 PM, ariekenb <aa...@lmco.com>
> wrote:
>>
>> I two beans named producer and consumer. Producer starts a
>> java.util.Timer
>> in its init method to pop every 100 ms and send a message to a SEDA queue
>> (using a ProducerTemplate it got from @EndpointInject). Consumer has a
>> method to receive messages from the queue. Here's the camel route:
>>
>> <camel:camelContext
>> id="test">
>>
>> <camel:endpoint
>> id="sedaEndpoint"
>> uri="seda:test" />
>>
>> <camel:route>
>> <camel:from
>> uri="sedaEndpoint" />
>> <camel:to
>>
>> uri="bean:consumer?methodName=processMessage" />
>> </camel:route>
>>
>> </camel:camelContext>
>>
>>
>> I find sometimes just after Producer sends its first message, I get this
>> error logged. This happens before Consumer has received any messages:
>>
>> 09:22:35,087 | ERROR | da:test thread:1 | DeadLetterChannel
>> |
>> rg.apache.camel.processor.Logger 203 | Failed delivery for exchangeId:
>> ID-swim4/48409-1241619754977/0-0. On delivery attempt: 0 caught:
>> java.lang.IllegalStateException: No producer, this processor has not been
>> started!
>> java.lang.IllegalStateException: No producer, this processor has not been
>> started!
>> at
>> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:78)
>> at
>> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
>> at
>> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:185)
>> at
>> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:132)
>> at
>> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
>> at
>> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52)
>> at
>> org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:69)
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>> This doesn't seem to cause anything bad to happen. Even when this
>> exception
>> happens, Consumer still receives all messages from Producer in order.
>>
>> I'm just wondering why this happens. Is there a race condition during
>> startup so that Producer can get its endpoint injected before camel is
>> ready
>> to route messages to Consumer? Should I be concerned about this?
>> --
>> View this message in context:
>> http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23407604.html
>> Sent from the Camel - Users (activemq) mailing list archive at
>> Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
> Apache Camel Reference Card:
> http://refcardz.dzone.com/refcardz/enterprise-integration
> Interview with me:
> http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
>
>
--
View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23409362.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
Re: SEDA Component Exception: No producer, this processor has not
been started!
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yeah its a race condition. You can configure your timer fire bean to
wait eg some longer before it fires the first message.
As long as you use the DeadLetterChannel you should in fact not worry
as it does redeliveries so in the next attempt it will usually succeed
as the producer is started in the meantime. However if you disable
redelivery etc. then the first message will not be delivered and lost.
But it would be best to wait a little before sending the very first message.
Otherwise you can use some Camel API to find the processor and test
whether it is started with: isStarted()
On Wed, May 6, 2009 at 4:36 PM, ariekenb <aa...@lmco.com> wrote:
>
> I two beans named producer and consumer. Producer starts a java.util.Timer
> in its init method to pop every 100 ms and send a message to a SEDA queue
> (using a ProducerTemplate it got from @EndpointInject). Consumer has a
> method to receive messages from the queue. Here's the camel route:
>
> <camel:camelContext
> id="test">
>
> <camel:endpoint
> id="sedaEndpoint"
> uri="seda:test" />
>
> <camel:route>
> <camel:from
> uri="sedaEndpoint" />
> <camel:to
> uri="bean:consumer?methodName=processMessage" />
> </camel:route>
>
> </camel:camelContext>
>
>
> I find sometimes just after Producer sends its first message, I get this
> error logged. This happens before Consumer has received any messages:
>
> 09:22:35,087 | ERROR | da:test thread:1 | DeadLetterChannel |
> rg.apache.camel.processor.Logger 203 | Failed delivery for exchangeId:
> ID-swim4/48409-1241619754977/0-0. On delivery attempt: 0 caught:
> java.lang.IllegalStateException: No producer, this processor has not been
> started!
> java.lang.IllegalStateException: No producer, this processor has not been
> started!
> at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:78)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
> at
> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:185)
> at
> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:132)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
> at
> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52)
> at org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:69)
> at java.lang.Thread.run(Thread.java:619)
>
>
> This doesn't seem to cause anything bad to happen. Even when this exception
> happens, Consumer still receives all messages from Producer in order.
>
> I'm just wondering why this happens. Is there a race condition during
> startup so that Producer can get its endpoint injected before camel is ready
> to route messages to Consumer? Should I be concerned about this?
> --
> View this message in context: http://www.nabble.com/SEDA-Component-Exception%3A-No-producer%2C-this-processor-has-not-been-started%21-tp23407604p23407604.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
Interview with me:
http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress