Hi, Claus:
It's a exciting feature. Hoping it will be available sooner;
By the way, it seems the camel 3.0 decide to introduce some new features;
While I am using camel, I often meet some requirement which I think if camel
support it, things will be better;
I always feel embarrassed to raise t
I am using Apache ServiceMix 4.2.0. It is the version bundled with Fuse 4.3.
The version of the NMR is Apache ServiceMix NMR 1.2.0
HTH
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuthentication-is-null-tp3290948p3291204.html
Sent from the Camel - Users
Oh, which version of servicemix are you using?
It looks like camel-nmr component doesn't deal will the Authentiacation
token rightly.
On 12/3/10 11:36 AM, Olivier.Roger wrote:
The CamelAuthentication header appears when message is passing through the
NMR
Here is the route:
The CamelAuthentication header appears when message is passing through the
NMR
Here is the route:
--
View this message in context:
http://camel.465427.n5.nabble.com/Serialization-CamelAuth
On Fri, Dec 3, 2010 at 4:17 PM, ext2 wrote:
> Thanks a lot.
> It's really a good news to support dynamic support at runtime;
>
> Actually, many management requirement need a runtime-dynamic-deciding
> features beside Instrument;
>
> For example: trace will be another example fro dynamic support
Thanks a lot.
It's really a good news to support dynamic support at runtime;
Actually, many management requirement need a runtime-dynamic-deciding features
beside Instrument;
For example: trace will be another example fro dynamic support: temporary to
open the trace to check problem, and th
On Fri, Dec 3, 2010 at 4:09 PM, ext2 wrote:
> Thanks a lot.
>
> It's a bad newly, I truly need jmx ,but doesn't want Instrument features;
> But a good news is Claus advice to support dynamic configuration support for
> Instrument in camel 3.0.
>
You can set the level of gathering jmx performance
Can you post the route?
I think the header should not be set if the value is null.
Likewise the exchange holder should not warn if the value is null, but
just silently ignores it.
On Fri, Dec 3, 2010 at 3:48 PM, Olivier.Roger wrote:
>
> Yes this is a test case.
> I did not set any authenticati
Thanks a lot.
It's a bad newly, I truly need jmx ,but doesn't want Instrument features;
But a good news is Claus advice to support dynamic configuration support for
Instrument in camel 3.0.
Best regard
-Origin-
Sender: Willem Jiang [mailto:willem.ji...@gmail.com]
Date: 2010/12/3 20:2
Yes this is a test case.
I did not set any authentication, that is why I am surprised there is a
CamelAuthentication header present in the exchange.
I will trace the exchanges to locate more precisely where the header appears
and get back to you.
Thanks for your help
--
View this message in co
It is not normal, and reviewing the Camel code (2.6-SNAPSHOT, not the
2.4.0.fuse-00-00 you're using), I don't see where this could have happened.
What do you use for authentication, spring-security? Is there a test case?
Thanks
Hadrian
On Dec 3, 2010, at 9:23 AM, Olivier.Roger wrote:
>
> Hel
Hello Camel,
I get this error in the log when I try to serialize my Exchanges with the
DefaultExchangeHandler:
DefaultExchangeHolder| camel.impl.DefaultExchangeHolder 210 |
69 - org.apache.camel.camel-core - 2.4.0.fuse-00-00 | in headers containing
object: null with key: CamelAuthen
On Fri, Dec 3, 2010 at 2:24 PM, Hadrian Zbarcea wrote:
> I did look at few examples. In your case, from looking at the log, it looks
> like it's wrapped twice, that's why is executed twice. The second number is
> always larger than the first. Since the Trace is an interceptor too, it looks
> li
I did look at few examples. In your case, from looking at the log, it looks
like it's wrapped twice, that's why is executed twice. The second number is
always larger than the first. Since the Trace is an interceptor too, it looks
like you got an instrument(trace(instrument(processor))). I will t
If you are using the Spring to create the camel context, you can disable
it by setting the jmxAgent attribute to be false.
If you create the camel context yourself, you can call the disableJMX()
method to do it.
On 11/30/10 9:18 PM, ext2 wrote:
Hi:
Camel's InstrumentationStrategy wi
Sorry, I forget to attach my tracing result;
I am sure , it's wrapped twice;
Because the Instrument Processor will trace the time only after
processing. But one processor 's instrument result is traced twice;
Following is my tracing output, you can check it.
- bean: Recording duration: 2
Hi.
I think one way to do this is:
onException(OutOfMemoryError.class)
.to(xxx);
You can replace xxx with a component that fits best for your case.
Perhaps a bean call if you've something like a spring context.
Best regards - Claus
On 03.12.2010 11:37, Andreas A. wrote:
Hi
I have a standa
Thanks Harian Zbarcea:
Instrument will be useful. But being wrapped and execute twice for
single processor will be a waste;
Actually, I found this problem while debug and tracing a spring
configured camel route. At least in Camel 2.4.0 and using spring, it real
does wrap twice.
Hi
I have a standalone Camel application:
A java main method with a Camel Main class that starts two different
contexts.
In case of an OutOfMemoryError I would like to propagate this Error from
Camel to the enclosing java main method. How can I propagate Errors and
Exceptions "out" of the Camel
Hi.
You can use camel in your java class like this:
@EndpointInject(uri="direct:start")
protected ProducerTemplate start;
...
start.sendBody(body);
The route should look like this:
from("direct:start") // This is a java class and the message is a java object.
.choice()
.when(simple("${bod
Hi,
The consumer is a java class and I'm passing a java VO to the producer(s)
depending on certain parameters in the VO.
from(endPoint) // This is a java class and the message is a java object.
.choice()
.when(simple("${body.ID}=='A'")).to("serverX")
.when(simple("${body.ID}=='B'")).to("serverY
21 matches
Mail list logo
