You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "dr.jeff" <jl...@systechnologies.com> on 2007/04/19 21:30:19 UTC
[camel] Splitter problem
When I do this:
from("queue:a").to("queue:b", "queue:c");
from("queue:b").process(new StringProcessor());
I get this:
2007-04-19 12:28:12,616 ERROR [org.apache.camel.processor.DeadLetterChannel]
- On delivery attempt: 1 caught: java.lang.NullPointerException
java.lang.NullPointerException
at org.apache.camel.impl.DefaultExchange.copyFrom(DefaultExchange.java:59)
...
--
View this message in context: http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10085314
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [camel] Splitter problem
Posted by "dr.jeff" <jl...@systechnologies.com>.
Looks fixed. Thanks.
Hiram Chirino wrote:
>
> Just committed a fix that should make this go away. The
> DefaultExchange.copy() can now deal with null messages.
>
> On 4/19/07, dr.jeff <jl...@systechnologies.com> wrote:
>>
>> When I do this:
>> from("queue:a").to("queue:b", "queue:c");
>> from("queue:b").process(new StringProcessor());
>> I get this:
>> 2007-04-19 12:28:12,616 ERROR
>> [org.apache.camel.processor.DeadLetterChannel]
>> - On delivery attempt: 1 caught: java.lang.NullPointerException
>> java.lang.NullPointerException
>> at
>> org.apache.camel.impl.DefaultExchange.copyFrom(DefaultExchange.java:59)
>> ...
>> --
>> View this message in context:
>> http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10085314
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>
--
View this message in context: http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10088377
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: [camel] Splitter problem
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Just committed a fix that should make this go away. The
DefaultExchange.copy() can now deal with null messages.
On 4/19/07, dr.jeff <jl...@systechnologies.com> wrote:
>
> When I do this:
> from("queue:a").to("queue:b", "queue:c");
> from("queue:b").process(new StringProcessor());
> I get this:
> 2007-04-19 12:28:12,616 ERROR [org.apache.camel.processor.DeadLetterChannel]
> - On delivery attempt: 1 caught: java.lang.NullPointerException
> java.lang.NullPointerException
> at org.apache.camel.impl.DefaultExchange.copyFrom(DefaultExchange.java:59)
> ...
> --
> View this message in context: http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10085314
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: [camel] Splitter problem
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Could you paste the full exception.
On 4/19/07, dr.jeff <jl...@systechnologies.com> wrote:
>
> Recreate this by running a message through the buildWireTap test.
> Also, after DeadLetterChannel finishes its retries, it gets this:
> org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
> log:org.apache.camel.DeadLetterChannel:error due to:
> java.lang.NullPointerException
> at
> org.apache.camel.impl.DefaultCamelContext.resolveEndpoint(DefaultCamelContext.java:180)
> at
> org.apache.camel.util.ExchangeHelper.resolveEndpoint(ExchangeHelper.java:49)
> at
> org.apache.camel.processor.RecipientList.resolveEndpoint(RecipientList.java:63)
> at org.apache.camel.processor.RecipientList.process(RecipientList.java:57)
> ....
> There is no file "log" in META-INF/services/org/apache/camel/component in
> camel-core main resources, so I don't know what it's trying to do.
>
>
>
> dr.jeff wrote:
> >
> > When I do this:
> > from("queue:a").to("queue:b", "queue:c");
> > from("queue:b").process(new StringProcessor());
> > I get this:
> > 2007-04-19 12:28:12,616 ERROR
> > [org.apache.camel.processor.DeadLetterChannel] - On delivery attempt: 1
> > caught: java.lang.NullPointerException
> > java.lang.NullPointerException
> > at
> > org.apache.camel.impl.DefaultExchange.copyFrom(DefaultExchange.java:59)
> > ...
> >
>
> --
> View this message in context: http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10085889
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
>
--
Regards,
Hiram
Blog: http://hiramchirino.com
Re: [camel] Splitter problem
Posted by "dr.jeff" <jl...@systechnologies.com>.
Recreate this by running a message through the buildWireTap test.
Also, after DeadLetterChannel finishes its retries, it gets this:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
log:org.apache.camel.DeadLetterChannel:error due to:
java.lang.NullPointerException
at
org.apache.camel.impl.DefaultCamelContext.resolveEndpoint(DefaultCamelContext.java:180)
at
org.apache.camel.util.ExchangeHelper.resolveEndpoint(ExchangeHelper.java:49)
at
org.apache.camel.processor.RecipientList.resolveEndpoint(RecipientList.java:63)
at org.apache.camel.processor.RecipientList.process(RecipientList.java:57)
....
There is no file "log" in META-INF/services/org/apache/camel/component in
camel-core main resources, so I don't know what it's trying to do.
dr.jeff wrote:
>
> When I do this:
> from("queue:a").to("queue:b", "queue:c");
> from("queue:b").process(new StringProcessor());
> I get this:
> 2007-04-19 12:28:12,616 ERROR
> [org.apache.camel.processor.DeadLetterChannel] - On delivery attempt: 1
> caught: java.lang.NullPointerException
> java.lang.NullPointerException
> at
> org.apache.camel.impl.DefaultExchange.copyFrom(DefaultExchange.java:59)
> ...
>
--
View this message in context: http://www.nabble.com/-camel--Splitter-problem-tf3609288s2354.html#a10085889
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.