#x27; behavior or ways to
configure it's port behavior beyond the initial connection.
-Original Message-
From: Jim Pirkle [mailto:jim.pir...@gmail.com]
Sent: Sunday, October 30, 2016 9:55 AM
To: users@camel.apache.org
Subject: Re: Camel-ahc-ws netty runtime problems
I tried t
inal Message-
From: Jim Pirkle [mailto:jim.pir...@gmail.com]
Sent: Sunday, October 30, 2016 9:55 AM
To: users@camel.apache.org
Subject: Re: Camel-ahc-ws netty runtime problems
I tried the 2.18.0 state packages, but had compile errors. Decided to wait for
2.18.1 before trying to resolve problems
O
2.0.15.jar:na]
> at
> org.asynchttpclient.netty.NettyResponseFuture.getContent(NettyResponseFuture.java:188)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture.java:223)
> ~[async-http-client-2.0.15.jar:na]
>
... 24 common frames omitted
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Friday, October 28, 2016 3:20 AM
To: users@camel.apache.org
Subject: Re: Camel-ahc-ws netty runtime problems
When using Spring Boot and Camel 2.18 onwards you should use the -star
When using Spring Boot and Camel 2.18 onwards you should use the
-starter components, eg camel-ahc-ws-starter and so on.
On Tue, Oct 25, 2016 at 8:21 PM, Ingram, Stuart wrote:
> Using the following dependencies
>
> compile('org.apache.camel:camel-jackson:2.18.0')
> compile('org.
Simplifying the route and removing multicast() & Pipeline() properties
results in no change.
Excluding the camel-ahc-ws netty dependencies and including them explicitly
in the build.gradle file also results in a runtime exception. This was
tested with netty-all.4.1.5.Final and netty-all.4.0.42.Fi
