Hi:
Camel support user to define custom InterceptStrategy;
But the exchanged processed by the custom interceptor's cannot be
logged by Camel's Tracer.
This is because camel always wrap tracer before wrapping the custom
interceptors;
Maybe camel should wrap tracer a
On Thu, Dec 9, 2010 at 5:22 PM, Remi Malessa wrote:
> On 12/09/2010 02:57 PM, Claus Ibsen wrote:
>>
>> Add some system out or something to see if it pickup your type converter.
>>
>> And mind that Camel can only choose your type converter if the message
>> body matches that type.
>> So make sure t
Hi, I have the following route defined -
from("timer://foo?period=5000").setBody(constant("select top 500 * from
MyTable where processed = 0"))
.to("jdbc:dataSource").split(body()).parallelProcessing()
.process(new MyProcessor()).unmarshal(jaxb)
Camel 3.0 will switch to use slf4j which has such a feature as well.
On Fri, Dec 10, 2010 at 5:30 AM, damianharvey wrote:
>
> Log4j has a nice feature where you can throw variables into the MDC static
> class and refer to them in the ConversionPattern in your log4j.properties.
>
> I am using thi
Log4j has a nice feature where you can throw variables into the MDC static
class and refer to them in the ConversionPattern in your log4j.properties.
I am using this to store an AuditId that I take from a SOAP header. Ideally
I'd like all log messages to be printed out with this AuditId however o
I think you need to set the mode back to PAYLOAD mode inside the second
processor (convertResponse) until CAMEL-3420 is fixed and delivered. I
added a unit test for your reference.
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/Cx
Thank you Claus!
--
View this message in context:
http://camel.465427.n5.nabble.com/Do-I-have-to-give-a-ScheduledExecutorService-instance-when-initializing-DefualtTimeoutMap-tp3298252p3299236.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On 12/09/2010 02:57 PM, Claus Ibsen wrote:
Add some system out or something to see if it pickup your type converter.
And mind that Camel can only choose your type converter if the message
body matches that type.
So make sure the body isn't wrapped into something else.
It is not picking up the or
On Thu, Dec 9, 2010 at 3:46 PM, Remi Malessa wrote:
> Hi Claus.
>
> I've put my class in a jar and placed it in my ActiveMQ_home/lib folder.
> Additionally I've placed a file called TypeConverter in
> /META-INF/services/org/apache/camel/ directory of the jar
> package.
>
> Inside the file I've put
Hi Claus.
I've put my class in a jar and placed it in my ActiveMQ_home/lib folder.
Additionally I've placed a file called TypeConverter in
/META-INF/services/org/apache/camel/ directory of the jar
package.
Inside the file I've put the package name of my type converter.
I've tested the String
On Thu, Dec 9, 2010 at 3:15 PM, Remi Malessa wrote:
> Hi .
>
> I've created a String to org.jdom.Document and org.jdom.Document to String
> type converter.
> The trouble is the org.jdom.Document doesn't seem to work.
>
> The converter code seems to be fine , as I tested it using the main method
>
Hi .
I've created a String to org.jdom.Document and org.jdom.Document to
String type converter.
The trouble is the org.jdom.Document doesn't seem to work.
The converter code seems to be fine , as I tested it using the main
method and it returns what I need.
But whether I output a message with
Hi Claus,
Here are the results of the tests I run:
Producer Only: 10msg/sec (transacted=true) / 2800 msg/sec
(transacted=false).
Consumer Only: 10msg/sec transacted=true) / ~500 msg/sec (transacted=false).
The results of the mixed is the ones I initially posted.
The difference is so big and I
Thanks for your suggestions , I will give them a try.
I did find that adding maxReconnectAttempts to the failover protocol would
allow an error to be thrown after a number of failed reconnect attempts.
Our users just wanted some indication that the activeMq service had not been
started.
The serv
Thanks Claus, this works:
${body.size} > 0
When using transacted=true then the commit is sync, and thus the
consumer side is impacted.
So you should be able to send as fast as you can. But the consumer
side is slower due the begin/commit pair in the transaction is
synchronous.
If you use camel-jms on the consumer side to consume and proce
I think that when I set "transacted=true" then it ignores the property
"useAsyncSend=true" set on the connection factory.
I am not sure if those two properties can be used together, but they
probably can't and this why I have performance issues.
On Tue, Dec 7, 2010 at 3:46 PM, Ioannis Canellos
Hi
Could you create a ticket in JIRA? There is a SMX NMR project
https://issues.apache.org/jira/browse/SMX4NMR
On Mon, Dec 6, 2010 at 9:41 AM, Olivier.Roger wrote:
>
> I also remarked that using the NMR adds another entry in the exchange header
> : NMRMessage which holds a copy of the message b
18 matches
Mail list logo
