You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Marvin <mg...@novomind.com> on 2016/10/31 14:14:01 UTC
camel 2.18.0 VM problem after update
I updated my camel version from 2.15.2 to 2.18.0. I'm using the vm component
to send messages through different contexts.
After the update I got following exception:
o.a.c.c.v.VmConsumer | Error processing exchange. Exchange[]. Caused by:
[java.lang.NullPointerException - null]
java.lang.NullPointerException: null
at
org.apache.camel.util.ExchangeHelper.isStreamCachingEnabled(ExchangeHelper.java:657)
at
org.apache.camel.converter.stream.OutputStreamBuilder.<init>(OutputStreamBuilder.java:38)
at
org.apache.camel.converter.stream.OutputStreamBuilder.withExchange(OutputStreamBuilder.java:55)
at
org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:58)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
I've found out that the problem the corresponding context to which the
exchange is set to is. It's using the route id of my vm enpoint and trying
to get the route out of the original context of the exchange. But it cannot
find the route because it isn't defined in the original context of the
exchange.
With the version 2.15.2 it's working fine.
Does anyone have an idea how I can fix this?
Thanks
Marvin
--
View this message in context: http://camel.465427.n5.nabble.com/camel-2-18-0-VM-problem-after-update-tp5789519.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel 2.18.0 VM problem after update
Posted by Marvin <mg...@novomind.com>.
Hi,
I cloned the repository and tried to build it with maven, but unfortunately
I got errors within the camel-soap component:
\camel-soap\target\generated\src\test\java\com\example\soapheaders\SampleEnumType.java:[4,3]
error: unmappable character for encoding UTF-8
\camel-soap\target\generated\src\test\java\com\example\soapheaders\SampleEnumType.java:[17,19]
error: unmappable character for encoding UTF-8
\camel-soap\target\generated\src\test\java\com\example\contact\ContactType.java:[4,3]
error: unmappable character for encoding UTF-8
...
--
View this message in context: http://camel.465427.n5.nabble.com/camel-2-18-0-VM-problem-after-update-tp5789519p5789636.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel 2.18.0 VM problem after update
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Maybe this bug fixes this
https://issues.apache.org/jira/browse/CAMEL-10406
You can build latest code and test with a SNAPSHOT version
http://camel.apache.org/building
On Mon, Oct 31, 2016 at 3:14 PM, Marvin <mg...@novomind.com> wrote:
> I updated my camel version from 2.15.2 to 2.18.0. I'm using the vm component
> to send messages through different contexts.
>
> After the update I got following exception:
>
> o.a.c.c.v.VmConsumer | Error processing exchange. Exchange[]. Caused by:
> [java.lang.NullPointerException - null]
> java.lang.NullPointerException: null
> at
> org.apache.camel.util.ExchangeHelper.isStreamCachingEnabled(ExchangeHelper.java:657)
> at
> org.apache.camel.converter.stream.OutputStreamBuilder.<init>(OutputStreamBuilder.java:38)
> at
> org.apache.camel.converter.stream.OutputStreamBuilder.withExchange(OutputStreamBuilder.java:55)
> at
> org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:58)
> at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
>
> I've found out that the problem the corresponding context to which the
> exchange is set to is. It's using the route id of my vm enpoint and trying
> to get the route out of the original context of the exchange. But it cannot
> find the route because it isn't defined in the original context of the
> exchange.
>
> With the version 2.15.2 it's working fine.
>
> Does anyone have an idea how I can fix this?
>
> Thanks
>
> Marvin
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-2-18-0-VM-problem-after-update-tp5789519.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: camel 2.18.0 VM problem after update
Posted by souciance <so...@gmail.com>.
Can you share how you send and receive to compare? It works for me on
2.17.0.
Den 31 okt. 2016 3:14 em skrev "Marvin [via Camel]" <
ml-node+s465427n5789519h52@n5.nabble.com>:
> I updated my camel version from 2.15.2 to 2.18.0. I'm using the vm
> component to send messages through different contexts.
>
> After the update I got following exception:
>
> o.a.c.c.v.VmConsumer | Error processing exchange. Exchange[]. Caused by:
> [java.lang.NullPointerException - null]
> java.lang.NullPointerException: null
> at org.apache.camel.util.ExchangeHelper.isStreamCachingEnabled(ExchangeHelper.java:657)
>
> at org.apache.camel.converter.stream.OutputStreamBuilder.<
> init>(OutputStreamBuilder.java:38)
> at org.apache.camel.converter.stream.OutputStreamBuilder.
> withExchange(OutputStreamBuilder.java:55)
> at org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:58)
>
> at org.apache.camel.management.InstrumentationProcessor.process(
> InstrumentationProcessor.java:77)
>
> I've found out that the problem the corresponding context to which the
> exchange is set to is. It's using the route id of my vm enpoint and trying
> to get the route out of the original context of the exchange. But it cannot
> find the route because it isn't defined in the original context of the
> exchange.
>
> With the version 2.15.2 it's working fine.
>
> Does anyone have an idea how I can fix this?
>
> Thanks
>
> Marvin
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/camel-2-18-0-VM-problem-
> after-update-tp5789519.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428h31@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://camel.465427.n5.nabble.com/camel-2-18-0-VM-problem-after-update-tp5789519p5789525.html
Sent from the Camel - Users mailing list archive at Nabble.com.