Hi Yeah I have logged a ticket about this a while back. For example if you try the camel-twitter example.
There is also camel-ahc-ws and camel-atmospwhere for websocket, they may work better. But of course if anyone got time to dive in and fix the bug in camel-websocket. It used to work before a big commit to add SSL support in it On Thu, Dec 4, 2014 at 5:36 PM, sbarie <sba...@mitre.org> wrote: > Created a simple route to consume messages from a websocket. For example: > > from (websocket://192.168.24.132:9101/mySocket) > .to(MyBean.class) > > Route works great initially. But if I stop the route and restart it.....the > route starts but clients can no longer connect to the socket. If I restart > ASM the route once again works just fine. Did quite a bit of searching but > was unable to find anything on this. > > Is this a bug or am I doing something wrong? Any help would be greatly > appreciated.... > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/A-restarted-websocket-endpoint-no-longer-accepts-client-connections-tp5760156.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
