I do not believe the port is already taken as I am able to connect and communicate at this address and on this port using java.net.Socket. I have worked around this issue by implement a custom Camel component that uses java.net.Socket and bypasses Netty completely. I believe this is a limitation of camel-netty, documented here: https://issues.apache.org/jira/browse/CAMEL-1077
Namaste On Mon, Aug 22, 2011 at 6:57 AM, Ashwin Karpe [via Camel] < [email protected]> wrote: > Hi, > > Based on the error, it seems that the port in question is already taken by > the another process and hence you cannot seem to set up a netty tcp consumer > against the given port. > > Can you try another port. > > Cheers, > > Ashwin... > --------------------------------------------------------- > Ashwin Karpe > Apache Camel Committer & Sr Principal Consultant > FUSESource (a Progress Software Corporation subsidiary) > http://fusesource.com > > Blog:http://opensourceknowledge.blogspot.com > --------------------------------------------------------- > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://camel.465427.n5.nabble.com/two-way-communication-with-TCP-server-using-Netty-tp4702360p4723317.html > To unsubscribe from two way communication with TCP server using Netty, click > here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4702360&code=bmFtYXN0ZS5yZWlkQG9wc3lzaW5jLmNvbXw0NzAyMzYwfDMzMjY2NTQzMA==>. > > -- View this message in context: http://camel.465427.n5.nabble.com/two-way-communication-with-TCP-server-using-Netty-tp4702360p4723395.html Sent from the Camel - Users mailing list archive at Nabble.com.
