Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E631E7B3F for ; Fri, 14 Oct 2011 12:58:06 +0000 (UTC) Received: (qmail 54548 invoked by uid 500); 14 Oct 2011 12:58:06 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 54472 invoked by uid 500); 14 Oct 2011 12:58:06 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 54460 invoked by uid 99); 14 Oct 2011 12:58:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 12:58:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 12:57:58 +0000 Received: by vws5 with SMTP id 5so961563vws.3 for ; Fri, 14 Oct 2011 05:57:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gcVuKyQyoujyMCbA9bQZseSBfdQezKZhh7MGvtEWWBE=; b=bFfbHBV7VBchQF1P1mIYC2bM3zQIvtdPLQ4YCxIQEh5odohgYUYPK/3fxEuMbOO3RL wwHAE2ujLhHq+dnZAvRWugueWn2WrA7yMGs2yqxeIL8AQk74U+hDMQp4NoETKW9xRDcO CX3nFejISbnmUrzAs08VxXolZvLBFiSe85tY8= MIME-Version: 1.0 Received: by 10.52.30.130 with SMTP id s2mr8467192vdh.55.1318597057501; Fri, 14 Oct 2011 05:57:37 -0700 (PDT) Received: by 10.52.184.226 with HTTP; Fri, 14 Oct 2011 05:57:37 -0700 (PDT) In-Reply-To: References: <4E981EAC.8030104@apache.org> Date: Fri, 14 Oct 2011 16:57:37 +0400 Message-ID: Subject: Re: Embeded Tomcat using a Connector with a random port (port 0) From: Konstantin Kolinko To: Tomcat Developers List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org 2011/10/14 Mark Thomas : > If binding to a random port is to be supported I think it needs to be an > explicit choice - e.g. by setting a special value such as "auto" - and > ideally needs to be supported by all connectors. > 2011/10/14 Olivier Lamy : > Do we agree on the fact that after been started, the protocol handler > will update the connector.port field to make the real port used > available for use ? If it were port=0 then you would better define a separate getLocalPort() property. The "auto" value... how can that be? Connector.setPort() accepts integer, and it can also be accessed through JMX. There are several layers, and if you say "update its port number", which of them will update its member variable and which not, and what happens if connector is restarted e.g. through JMX? Also I would like to introduce support for "-1" value for port number, as I mentioned above, but that would be a separate feature. > I have opened https://issues.apache.org/bugzilla/show_bug.cgi?id=52028 > and will try to propose a patch next week. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org