Has anyone managed to integrate Camel logs with Logstash/Elasticsearch?
I've got tracer and MDC logging enabled in my CamelContext and am sending
logs to Logstash via log4j TCP appender. This is working great (especially
MDC fields), but I'm trying to further parse and filter the message to
I am using camel over a clustered environment and want to use a readlock on
my file consumer endpoint. The only cluster safe readlock is the idempotent
readlock however this requires an idempotentRepository to be set on the file
uri.
I use an idempotent consumer within the route which moves any
The syslog date format in log4j 2 is "MMM dd HH:mm:ss" (SimpleDateFormat
style).
On 7 October 2016 at 04:09, fabryprog wrote:
> Hello everyone,
>
> I'm trying to figure out how to set log4j conversionPattern to be
> compatible
> with the SyslogDateFormat.
>
> I try
Hello,
This is my camel scp test code.
I'd like to send a file to remote server with prefix "temp_".
After finishing scp file copy, the "temp_" prefix is supposed to be gone.
BUT the file name with tempPrefix never work. While writing, the file is
same with original file.
Did I miss
Can i have a test code or test mock project?
--
View this message in context:
http://camel.465427.n5.nabble.com/Calling-body-getXX-from-Simple-EL-taking-200-ms-tp5788478p5788481.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
I notice that when making method calls on the body using the Simple EL they
are quite slow depending on the size of the object on the exchange, e.g.
${body.getXX}
Is there anyway to speed this up?
Thanks
Joe
--
View this message in context:
Excuse me. Maybe I did not quite understand spoken. Or someone does not quite
understand.
On page http://camel.apache.org/file-language.html
file:modified - Refers to the file last modified returned as a Date type.
Writing
idempotentKey=${file:name}-${file:size}-${file:modified}
Hello everyone,
I'm trying to figure out how to set log4j conversionPattern to be compatible
with the SyslogDateFormat.
I try without results:
log4j.appender.syslog.layout.conversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m
log4j.appender.syslog.layout.conversionPattern=%d{ISO8601} %-5p [%t] %c{2}
Unfortunately it is not sufficient to provide own SearchTerm class and
overriding "match" because com.sun.mail.imap.protocol.SearchSequence checks
specific implementations of SearchTerm provided by com.sun.mail and all
implementations are final. I worked around the issue by resetting the