This means I cannot use camel-netty inside a vertx webapp... as they will try to bind the same local port :(
What could I do? Il 26/Ago/2014 13:28 "Willem.Jiang [via Camel]" < ml-node+s465427n5755699...@n5.nabble.com> ha scritto: > No, you cannot specify the local port when sending the request to server. > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On August 26, 2014 at 6:25:38 PM, edmondo1984 ([hidden email] > <http://user/SendEmail.jtp?type=node&node=5755699&i=0>) wrote: > > > I probably misexplained myself. > > > > I am connecting to a remote url: > > > > to ("netty:tcp://oneserver:129") > > > > This fails because the local port netty is using for the tcp connection > is > > already taken. > > > > I would need to tell netty: create a tcp connection from localhost:24563 > to > > oneserver:129 for example > > > > Thank you > > Il 26/Ago/2014 11:17 "Claus Ibsen-2 [via Camel]" < > > [hidden email] <http://user/SendEmail.jtp?type=node&node=5755699&i=1>> > ha scritto: > > > > > You set the port as part of the uri of the endpoint, etc > > > > > > netty:tcp://localhost:99999[?options] > > > > > > On Tue, Aug 26, 2014 at 12:14 PM, edmondo1984 <[hidden email] > > > > wrote: > > > > Thanks. I have read the documentation before posting and I didn't > find > > > it :( > > > > I suppose I am missing maybe some Netty know how? > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > http://camel.465427.n5.nabble.com/Camel-Netty-component-bind-failure-tp5755683p5755688.html > > > > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > > > > > > > > > -- > > > Claus Ibsen > > > ----------------- > > > Red Hat, Inc. > > > Email: [hidden email] > > > > > > Twitter: davsclaus > > > Blog: http://davsclaus.com > > > Author of Camel in Action: http://www.manning.com/ibsen > > > hawtio: http://hawt.io/ > > > fabric8: http://fabric8.io/ > > > > > > > > > ------------------------------ > > > If you reply to this email, your message will be added to the > discussion > > > below: > > > > > > > http://camel.465427.n5.nabble.com/Camel-Netty-component-bind-failure-tp5755683p5755689.html > > > > To unsubscribe from Camel Netty component bind failure, click here > > > > > > . > > > NAML > > > > > > > > > > > > > > > > -- > > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Netty-component-bind-failure-tp5755683p5755691.html > > > Sent from the Camel - Users mailing list archive at Nabble.com. > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/Camel-Netty-component-bind-failure-tp5755683p5755699.html > To unsubscribe from Camel Netty component bind failure, click here > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5755683&code=ZWRtb25kby5wb3JjdUBnbWFpbC5jb218NTc1NTY4M3w1ODk2MDQ2MzY=> > . > NAML > <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Netty-component-bind-failure-tp5755683p5755702.html Sent from the Camel - Users mailing list archive at Nabble.com.
