Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 432E68D38 for ; Mon, 22 Aug 2011 13:20:20 +0000 (UTC) Received: (qmail 9839 invoked by uid 500); 22 Aug 2011 13:20:19 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 9680 invoked by uid 500); 22 Aug 2011 13:20:19 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 9672 invoked by uid 99); 22 Aug 2011 13:20:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2011 13:20:19 +0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Aug 2011 13:20:12 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QvUPu-0004Zj-Ns for users@camel.apache.org; Mon, 22 Aug 2011 06:19:51 -0700 Date: Mon, 22 Aug 2011 06:19:50 -0700 (PDT) From: Namaste Reid To: users@camel.apache.org Message-ID: In-Reply-To: <1314017835742-4723317.post@n5.nabble.com> References: <1313441850903-4702360.post@n5.nabble.com> <1313499800196-4704343.post@n5.nabble.com> <1314017835742-4723317.post@n5.nabble.com> Subject: Re: two way communication with TCP server using Netty MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1870_19993016.1314019190734" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_1870_19993016.1314019190734 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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] < ml-node+4723317-1672245996-242140@n5.nabble.com> 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. > > -- 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. ------=_Part_1870_19993016.1314019190734--