Re: Camel-ahc-ws netty runtime problems

[Andrea Cosentino]

If you think the behavior of camel-websocket can be better you can fill a JIRA 
on Camel JIRA.

https://issues.apache.org/jira/browse/CAMEL

 --
Andrea Cosentino 
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd



On Sunday, October 30, 2016 5:55 PM, "Ingram, Stuart" <ingra...@upmc.edu> wrote:
Thanks Jim for looking into this.  Confirmation that it's broken vs something 
I'm doing wrong is a big time saver.  Will check back in on the next release.

The 'camel-websockets' package works for me to a certain degree but opens up 
multiple random ports per client connection making it completely unsuitable for 
my purposes unfortunately, hence the interest in 'ahc-ws'.  Didn't find much in 
the way of documentation on the 'camel-websockets' 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 the 2.18.0 state packages, but had compile errors. Decided to wait for 
2.18.1 before trying to resolve problems

On Fri, Oct 28, 2016, 8:55 PM Ingram, Stuart <ingra...@upmc.edu> wrote:

> Thanks Claus!  I wasn't aware of the *-starter packages for Camel.  
> Much appreciated for the pointer.
>
> Moving to the 'camel-ahc-ws-starter' package and adjusting all other
> camel* packages I now get a different exception.
>
> Any help/pointers are appreciated.  Thanks
>
>
> java.util.concurrent.ExecutionException: java.lang.IllegalStateException:
> Invalid Status Code 404
> at
> org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture
> .java:228)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.handler.WebSocketHandler$UpgradeCallback.cal
> l(WebSocketHandler.java:100)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(A
> syncHttpClientHandler.java:73)
> ~[async-http-client-2.0.15.jar:na]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstrac
> tChannelHandlerContext.java:345) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandler
> Context.fireChannelRead(CombinedChannelDuplexHandler.java:435)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMess
> ageDecoder.java:293) ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageD
> ecoder.java:267) ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChan
> nelDuplexHandler.java:250) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstrac
> tChannelHandlerContext.java:345) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(Defaul
> tChannelPipeline.java:1294) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannel
> Pipeline.java:911) ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(Abstrac
> tNioByteChannel.java:131) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> 

RE: Camel-ahc-ws netty runtime problems

[Ingram, Stuart]

Thanks Jim for looking into this.  Confirmation that it's broken vs something 
I'm doing wrong is a big time saver.  Will check back in on the next release.

The 'camel-websockets' package works for me to a certain degree but opens up 
multiple random ports per client connection making it completely unsuitable for 
my purposes unfortunately, hence the interest in 'ahc-ws'.  Didn't find much in 
the way of documentation on the 'camel-websockets' 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 the 2.18.0 state packages, but had compile errors. Decided to wait for 
2.18.1 before trying to resolve problems

On Fri, Oct 28, 2016, 8:55 PM Ingram, Stuart <ingra...@upmc.edu> wrote:

> Thanks Claus!  I wasn't aware of the *-starter packages for Camel.  
> Much appreciated for the pointer.
>
> Moving to the 'camel-ahc-ws-starter' package and adjusting all other
> camel* packages I now get a different exception.
>
> Any help/pointers are appreciated.  Thanks
>
>
> java.util.concurrent.ExecutionException: java.lang.IllegalStateException:
> Invalid Status Code 404
> at
> org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture
> .java:228)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.handler.WebSocketHandler$UpgradeCallback.cal
> l(WebSocketHandler.java:100)
> ~[async-http-client-2.0.15.jar:na]
> at
> org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(A
> syncHttpClientHandler.java:73)
> ~[async-http-client-2.0.15.jar:na]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstrac
> tChannelHandlerContext.java:345) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandler
> Context.fireChannelRead(CombinedChannelDuplexHandler.java:435)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMess
> ageDecoder.java:293) ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageD
> ecoder.java:267) ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChan
> nelDuplexHandler.java:250) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstrac
> tChannelHandlerContext.java:345) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(Defaul
> tChannelPipeline.java:1294) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:366)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abstr
> actChannelHandlerContext.java:352)
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannel
> Pipeline.java:911) ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(Abstrac
> tNioByteChannel.java:131) 
> ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java
> :611) ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEven
> tLoop.java:552) ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.jav
> a:466) ~[netty-transport-4.0.41.Fina

Re: Camel-ahc-ws netty runtime problems

[Jim Pirkle]

 
> org.asynchttpclient.ws.WebSocketUpgradeHandler.onCompleted(WebSocketUpgradeHandler.java:29)
> ~[async-http-client-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 -starter
> components, eg camel-ahc-ws-starter and so on.
>
>
>
> On Tue, Oct 25, 2016 at 8:21 PM, Ingram, Stuart <ingra...@upmc.edu> wrote:
> > Using the following dependencies
> >
> > compile('org.apache.camel:camel-jackson:2.18.0')
> > compile('org.apache.camel:camel-metrics:2.18.0')
> > compile('org.apache.camel:camel-spring-boot-starter:2.18.0')
> > compile('org.apache.camel:camel-spring-redis:2.18.0')
> > compile('org.apache.camel:camel-stream:2.18.0')
> > compile('org.apache.camel:camel-ahc-ws:2.18.0')
> > compile('org.springframework.boot:spring-boot-actuator')
> > compile("org.springframework.boot:spring-boot-starter-web")
> >
> > And the following ahc-ws definition in Spring Boot
> >
> > .
> > .multicast()
> > .parallelProcessing()
> >
> > .pipeline()
> > .marshal().json(JsonLibrary.Jackson)
> > .convertBodyTo(String.class)  // Avoids string serialization
> issues in websocket component.
> > .to("ahc-ws://localhost:8080/votes?sendToAll=true")
> > .end()
> > .
> >
> > At runtime I get the following error when publishing to this sink
> >
> > 2016-10-25 11:41:45.689  INFO 1864 --- [ #7 - Multicast]
> o.a.camel.component.ahc.ws.WsEndpoint: Reconnecting websocket:
> ws://localhost:8080/votes?sendToAll=true
> > 2016-10-25 11:41:45.777 ERROR 1864 --- [ #7 - Multicast]
> > o.a.camel.processor.DefaultErrorHandler  : Failed delivery for
> > (MessageId: ID-singram-mint172-42019-1477410101007-0-56 on ExchangeId:
> > ID-singram-mint172-42019-1477410101007-0-59). Exhausted after delivery
> > attempt: 1 caught: java.util.concurrent.ExecutionException:
> > java.net.ConnectException:
> > io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/Defau
> > ltChannelId;
> >
> > java.util.concurrent.ExecutionException: java.net.ConnectException:
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> > at
> org.asynchttpclient.netty.NettyResponseFuture.abort(NettyResponseFuture.java:239)
> ~[async-http-client-2.0.15.jar:na]
> > at
> org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:162)
> ~[async-http-client-2.0.15.jar:na]
> > at
> org.asynchttpclient.netty.request.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:103)
> ~[async-http-client-2.0.15.jar:na]
> > at
> org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)
> ~[async-http-client-2.0.15.jar:na]
> > at
> org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)
> ~[async-http-client-2.0.15.jar:na]
> > at
> io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:514)
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> > at
> io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:488)
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> > at
> io.netty.util.concurrent.DefaultPromise.access$000(DefaultPromise.java:34)
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> > at
> io.netty.util.concurrent.DefaultPromise$1.run(DefaultPromise.java:438)
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> > at
> io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run(GlobalEventExecutor.java:233)
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> > at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91] Caused
> > by: java.net.ConnectException:
> io.netty.channel.DefaultChannel

RE: Camel-ahc-ws netty runtime problems

[Ingram, Stuart]

Thanks Claus!  I wasn't aware of the *-starter packages for Camel.  Much 
appreciated for the pointer.

Moving to the 'camel-ahc-ws-starter' package and adjusting all other camel* 
packages I now get a different exception. 

Any help/pointers are appreciated.  Thanks


java.util.concurrent.ExecutionException: java.lang.IllegalStateException: 
Invalid Status Code 404
at 
org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture.java:228)
 ~[async-http-client-2.0.15.jar:na]
at 
org.asynchttpclient.netty.handler.WebSocketHandler$UpgradeCallback.call(WebSocketHandler.java:100)
 ~[async-http-client-2.0.15.jar:na]
at 
org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:73)
 ~[async-http-client-2.0.15.jar:na]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:435)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
 ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
 ~[netty-codec-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:250)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:345)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1294)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:366)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:352)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:911)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:611) 
~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:552)
 ~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:466) 
~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:438) 
~[netty-transport-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:140)
 ~[netty-common-4.0.41.Final.jar:4.0.41.Final]
at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
 ~[netty-common-4.0.41.Final.jar:4.0.41.Final]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
Caused by: java.lang.IllegalStateException: Invalid Status Code 404
at 
org.asynchttpclient.ws.WebSocketUpgradeHandler.onCompleted(WebSocketUpgradeHandler.java:81)
 ~[async-http-client-2.0.15.jar:na]
at 
org.asynchttpclient.ws.WebSocketUpgradeHandler.onCompleted(WebSocketUpgradeHandler.java:29)
 ~[async-http-client-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

Re: Camel-ahc-ws netty runtime problems

[Claus Ibsen]

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.apache.camel:camel-metrics:2.18.0')
> compile('org.apache.camel:camel-spring-boot-starter:2.18.0')
> compile('org.apache.camel:camel-spring-redis:2.18.0')
> compile('org.apache.camel:camel-stream:2.18.0')
> compile('org.apache.camel:camel-ahc-ws:2.18.0')
> compile('org.springframework.boot:spring-boot-actuator')
> compile("org.springframework.boot:spring-boot-starter-web")
>
> And the following ahc-ws definition in Spring Boot
>
> .
> .multicast()
> .parallelProcessing()
>
> .pipeline()
> .marshal().json(JsonLibrary.Jackson)
> .convertBodyTo(String.class)  // Avoids string serialization issues 
> in websocket component.
> .to("ahc-ws://localhost:8080/votes?sendToAll=true")
> .end()
> .
>
> At runtime I get the following error when publishing to this sink
>
> 2016-10-25 11:41:45.689  INFO 1864 --- [ #7 - Multicast] 
> o.a.camel.component.ahc.ws.WsEndpoint: Reconnecting websocket: 
> ws://localhost:8080/votes?sendToAll=true
> 2016-10-25 11:41:45.777 ERROR 1864 --- [ #7 - Multicast] 
> o.a.camel.processor.DefaultErrorHandler  : Failed delivery for (MessageId: 
> ID-singram-mint172-42019-1477410101007-0-56 on ExchangeId: 
> ID-singram-mint172-42019-1477410101007-0-59). Exhausted after delivery 
> attempt: 1 caught: java.util.concurrent.ExecutionException: 
> java.net.ConnectException: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
>
> java.util.concurrent.ExecutionException: java.net.ConnectException: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> at 
> org.asynchttpclient.netty.NettyResponseFuture.abort(NettyResponseFuture.java:239)
>  ~[async-http-client-2.0.15.jar:na]
> at 
> org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:162)
>  ~[async-http-client-2.0.15.jar:na]
> at 
> org.asynchttpclient.netty.request.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:103)
>  ~[async-http-client-2.0.15.jar:na]
> at 
> org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)
>  ~[async-http-client-2.0.15.jar:na]
> at 
> org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)
>  ~[async-http-client-2.0.15.jar:na]
> at 
> io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:514)
>  ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:488)
>  ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.util.concurrent.DefaultPromise.access$000(DefaultPromise.java:34) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.util.concurrent.DefaultPromise$1.run(DefaultPromise.java:438) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.util.concurrent.GlobalEventExecutor$TaskRunner.run(GlobalEventExecutor.java:233)
>  ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
>  ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_91]
> Caused by: java.net.ConnectException: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> at 
> org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:160)
>  ~[async-http-client-2.0.15.jar:na]
> ... 10 common frames omitted
> Caused by: java.lang.NoSuchMethodError: 
> io.netty.channel.DefaultChannelId.newInstance()Lio/netty/channel/DefaultChannelId;
> at io.netty.channel.AbstractChannel.newId(AbstractChannel.java:107) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at io.netty.channel.AbstractChannel.(AbstractChannel.java:79) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.channel.nio.AbstractNioChannel.(AbstractNioChannel.java:84) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.channel.nio.AbstractNioByteChannel.(AbstractNioByteChannel.java:54)
>  ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.channel.socket.nio.NioSocketChannel.(NioSocketChannel.java:98) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> io.netty.channel.socket.nio.NioSocketChannel.(NioSocketChannel.java:88) 
> ~[netty-all-4.1.5.Final.jar:4.1.5.Final]
> at 
> 

Re: Camel-ahc-ws netty runtime problems

[Stuart]

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.Final

This looks to me like a bug at this time.  Anyone else have the same
experience?

Thanks
- Stuart



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-ahc-ws-netty-runtime-problems-tp5789236p5789366.html
Sent from the Camel - Users mailing list archive at Nabble.com.