Hi Maybe there is some old code with 9292 or and old java / jvm process running that take up the old port, or something.
On Sun, Apr 16, 2017 at 5:49 AM, contactreji <[email protected]> wrote: > Hello guys > > I am doing a POC on camel websockets. I have some data being pushed from UI > layer over websockets > > from("websocket://0.0.0.0:9293/hotelsearch") > .log(LoggingLevel.INFO,"TestServices","Received Search > Request data ${body}") > .removeHeaders("*") > .to("direct:Authenticate")...... and so On... > > This deploys perfectly fine as long as I have no other modules deployed on > the same server. ( Deployed as a springboot application). Another project is > running on same server which binds to 9292 for its websocket consumer > endpoint . And for the above module I changed it to 9293 to avoid port > conflict. > > But surprisingly, when i start this app, it tries to bind port *9292* > instead of *9293* and as a result, I get port binding error. > > *Will not consumer endpoint like from(websocket://0.0.0.0:9293/hotelsearch) > bind to 9293? Why is it trying to bind to 9292? Could this be a bug in > Websocket Component? > * > Cheers > Reji > > > > > > ----- > Reji Mathews > Sr. Developer - Middleware Integration / SOA ( Open Source - Apache Camel & > Jboss Fuse ESB | Mule ESB ) > LinkedIn - http://in.linkedin.com/pub/reji-mathews/31/9a2/40a > Twitter - reji_mathews > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Websocket-Binding-error-tp5797760.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
