Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DD23A2007D0 for ; Tue, 10 May 2016 14:28:24 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DBC48160877; Tue, 10 May 2016 12:28:24 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5498F1607AA for ; Tue, 10 May 2016 14:28:24 +0200 (CEST) Received: (qmail 69742 invoked by uid 500); 10 May 2016 12:28:23 -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 69727 invoked by uid 99); 10 May 2016 12:28:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 May 2016 12:28:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id B624EC0141 for ; Tue, 10 May 2016 12:28:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.486 X-Spam-Level: *** X-Spam-Status: No, score=3.486 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id d8BNDcrFGJWq for ; Tue, 10 May 2016 12:28:20 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTP id 185735F19B for ; Tue, 10 May 2016 12:28:19 +0000 (UTC) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id D64032737D80 for ; Tue, 10 May 2016 05:12:37 -0700 (PDT) Date: Tue, 10 May 2016 05:28:19 -0700 (MST) From: souciance To: users@camel.apache.org Message-ID: <1462883299576-5782404.post@n5.nabble.com> Subject: Camel netty tcp new instance for each client connection MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Tue, 10 May 2016 12:28:25 -0000 Hello, I have a scenario where in a Camel route I have a from ("netty4:tcp") which listens on a ip:port. Clients can connect to it and send string messages. The first message each client sends identifies who they are. Subsequent messages are normal payload. However the backend system needs the identifier each time. My question is, how is it possible to identify when a client connections to the route and have a "seperate pipeline" or session for that particular client sending messages, and a new pipeline or session when another client starts connection? Is this possible? Thanks Best Souciance -- View this message in context: http://camel.465427.n5.nabble.com/Camel-netty-tcp-new-instance-for-each-client-connection-tp5782404.html Sent from the Camel - Users mailing list archive at Nabble.com.