Re: camel-aws-xray doesn't play well with XRay segments created beforehand

Hi Tom, I'm the original author of that component but I have to say that I'm no longer working for the team that initially experimented with it. Since then our technology stack furthermore changed and we ditched AWS XRay in our monitoring efforts completely. My current position also has hardly

Re: Passwords in Camel endpoint URIs and limitations of RAW syntax

Hi Florian, if you're concerned about logging sensitive data, I'd recommend to configure your logging framework to filter such sensitive information in first place as the sensitive information might otherwise leak through other means not in control of Camel itself, i.e. as logged directly from

Re: Camel-jetty http/2 support

Jetty 9.4 does support HTTPS/2: https://www.eclipse.org/jetty/documentation/9.4.x/http2.html Undertow does support it in version 2 AFAIK: http://undertow.io/blog/2015/04/27/An-in-depth-overview-of-HTTP2.html Roman Vottner — ecosio GmbH Lange Gasse 30, 1080 Vienna, Austria/Europe Mail

Re: Jetty consumer responds with a 500 error java.io.IOException: Response header too large

Do you somehow store the received file into camel headers? Camel will return most headers to the invoker and usually HTTP headers > 8kb will produce that kind of exception. You might want to introduce a customized HttpHeaderFilterStrategy similar to the sample below to avoid returning certain

Re: difference on seda versus threads usage

To my knowledge the latter one will create a new exchange for each seda invoked route and copy over the data from the origin exchange while the primer one will just create threads within an executor service (no new exchange creation) and thus use the same exchange. You might see a difference

Re: Send messages to remote SSL/TLSv1.2 enabled rest endpoints?

Are you attempting an SSL connection with a self-signed certificate? I guess the server endpoints are working fine via https if accessed via a browser? You should follow this guide (https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html

Re: http4 component with spring boot to configure ssl parameters

Hi Steve, you basically have to define some SSLContextParameters and add them to your HttpComponent as hopefully can be seen in the URL below https://github.com/RovoMe/camel-rest-dsl-with-spring-security/blob/master/src/main/java/at/rovo/awsxray/config/HttpClientSpringConfig.java

Re: REST DSL process multipart/form-data binary file?

l 2.19.3 and observed the same problem so I don't think a > newer version of Camel fixes things. What environment are you running your > code inside? > > > > > > On Sat, Sep 30, 2017 at 9:13 PM, Roman Vottner <[hidden email] > > wrote

Re: REST DSL process multipart/form-data binary file?

Our Camel REST DSL configuration looks like this: onException(Exception.class) .handled(true) .logExhausted(false) .log(LoggingLevel.ERROR, ">> In default/message exception handler. ${exception}, message: ${exception.message}, stacktrace: ${exception.stacktrace}")

Add ServletFilter to invoked Jetty component

I’ve pushed a sample test application onto github (https://github.com/RovoMe/camel-rest-dsl-with-spring-security ) where I want to integrate AWS XRay servlet filter for any inbound or outbound traffic. Spring Security offers the

Re: A lot of spam

So what to use instead? Github issues? Stackoverflow posts? Shouldn’t this be communicated to users and eventually also lead to a shutdown of Camel’s nabble mailing list? > Am 21.08.2017 um 23:51 schrieb Claus Ibsen : > > Yes we have given up on nabble - do not use it.

Re: 2.19.0 Jetty:Https javax.net.ssl.SSLHandshakeException: no cipher suites in common

Hi, Camel 2.19.0 upgraded its Jetty9 version to 9.3.x which only supports TLSv1.2 out of the box. As all ciphers used for TLSv1 (and TLSv1.1) are considered unsafe they get blocked by Jetty9 now and hence no ciphers are available in case of TLSv1 or TLSv1.1. connection attempts. (See

Testing rainy-cases of consumers consuming in an own thread

We have a custom Camel component named CamelRedisSeda which basically is an extension of UriEndpointComponent, which pops items from or pushes items to a Redis queue. For testing both Redis client and the connection are mocked and use a blocking queue in the back as Redis queue replacement. I

Log raw requests and responses received via a Jetty endpoint

We run a couple of Jetty servers through Camel and are curious if Camel provides any built-in facilities to log the raw HTTP request and also the response. We’d like an output similar to the one of an Apache HTTP Client (log messages for org.apache.http.wire) where an output may look like this:

Validation on build time of camel component fails when component has some getter/setters

Hi there, we use Camel 2.16.0 and are currently developing a Camel component and on trying to build an artifact using „mvn clean install“ or „mvn clean package“ the build fails due to: Missing component documentation for the following options: … as the component class defines a getter and

Re: Rest DSL with jetty and SSL

I've had similar problems (http://camel.465427.n5.nabble.com/Rest-DSL-how-to-configure-SSL-Basic-Auth-for-Jetty-component-td5758003.html) and therefore created a github project (https://github.com/RovoMe/CamelMultipleJettyComponents/tree/rest-dsl) to test Camel's REST-DSL with SSL/Basic Auth

Re: Rest DSL - how to configure SSL/Basic Auth for jetty component?

you have configured on it. And I think we have fixed the double ? in the uri in the upcoming 2.14.1 release. On Wed, Nov 5, 2014 at 10:53 AM, Roman Vottner r...@gmx.at wrote: This is a repost of the nabble forum entry as my account was obviously not correctly verified at the time when I

Rest DSL - how to configure SSL/Basic Auth for jetty component?

This is a repost of the nabble forum entry as my account was obviously not correctly verified at the time when I posted this issue (post has NOT been accepted …). In order to test the new REST feature in 2.14.0 I created a simple route class: public class RestTestRoute extends RouteBuilder {

StackOverflowError on configuring JettyHttpComponents with handlers for the same port

We upgraded from Camel 2.13.0 to 2.14.0 a couple of days ago and noticed some problems during the upgrade. While we managed to fix certain issues with CXF based services in Camel (extending spring configurations didn’t work for us in 2.14.0 but using @Import({…}) does achieve the same), we