Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of yoavnaveh@gmail.com
 designates 209.85.212.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=T7DZd9TDJ441ASxlznCfRdV+uoUDwe00xxtkkX7ckn4g9QgGz/Dy6pE/X0SniP4xHf
         ScwkTBal7DmdebBDT72yFX1J9rwmuOCHgKRgALwljVSmqDl5UMGZaJwqLrIUaklGGuof
         lQT6EscnzBuBcwmOzvjuVA/OdA8cSqWVzElJY=
MIME-Version: 1.0
Date: Wed, 1 Sep 2010 09:59:20 +0300
Message-ID: <AANLkTinD_dU6yOLabgJC3sHZyv5CMb=Sb04YF3ZYoTUV@mail.gmail.com>
Subject: Slow "network" with additional Connector (Port) in tomcat
From: Yoav Naveh <yoavnaveh@gmail.com>
To: users@tomcat.apache.org
Content-Type: multipart/alternative; boundary=001636ef049c9f240e048f2d3c09

--001636ef049c9f240e048f2d3c09
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have come across a weird behavior. I defined an additional port for my
tomcat, by adding an additional connector in the server.xml
The connector was placed in the same container, and the only difference was
the new port.

Now, when I connect to my server using the old port (80) - network time is
standard. When I use the new custom port, I see much
longer network time. Analyzing the network shows that the difference is that
a new chunk of time is taken for "connection" and about the same time for
actually working with the server. To emphasize, the connections to port 80
still works ok, just the new port on that server works slowly.

Removing the port 80 connector altogether (leaving just the new one) did not
help.

Is there any default configuration for port 80 that should be duplicated for
a new port?
Any ideas would help.

Thanks!

--001636ef049c9f240e048f2d3c09--