Re: Slow network with additional Connector (Port) in tomcat

2010-09-02 Thread Yoav Naveh
Hi, thanks for your reply.

Some more information:
Tomcat is using OpenJdk6, on Ubuntu 8.04
I have attached my server.xml file. The only thing that comes to mind is
that I set a relatively low accept-count for the other port. I think we
tested without that parameter and did not getter better results. Let me know
if there is a high chance this is the issue

For the second set of questions: I ran the test on EC2, and verified on a
different environment that problem occurs there as well. ports are open,
nothing in iptables, I used direct IP address in my test and test client is
always the same browser from the same host.

Thanks!

On Wed, Sep 1, 2010 at 5:37 PM, Christopher Schultz 
ch...@christopherschultz.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Chuck,

 On 9/1/2010 9:33 AM, Caldarale, Charles R wrote:
  From: Yoav Naveh [mailto:yoavna...@gmail.com]
  Subject: Slow network with additional Connector (Port) in tomcat
 
  I have come across a weird behavior.
 
  Such as not telling us the exact Tomcat level you're using, the JVM
 version it's running in, the platform you're running on, and whether or not
 you're using APR, or anything in the logs that might be pertinent?
 
  I defined an additional port for my tomcat, by adding
  an additional connector in the server.xml
 
  So post your server.xml, with comments removed and secure information
 obfuscated, so we can see what you really did.

 It would also help to know what other network components are in place:
 software/hardware firewall, any iptables routing, reverse DNS settings,
 etc. Also, is the test client always on the same host?

 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.10 (MingW32)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAkx+ZToACgkQ9CaO5/Lv0PAYiACgjYDJVtNVStcoUijm/Qp8XQtP
 WAEAnR9AABDved7jrN1NT3uiku8/dsrr
 =HGNw
 -END PGP SIGNATURE-

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


?xml version='1.0' encoding='utf-8'?
!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the License); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an AS IS BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--
!-- Note:  A Server is not itself a Container, so you may not
 define subcomponents such as Valves at this level.
 Documentation at /docs/config/server.html
 --
Server port=8005 shutdown=SHUTDOWN

  !--APR library loader. Documentation at /docs/apr.html --
  Listener className=org.apache.catalina.core.AprLifecycleListener SSLEngine=on /
  !--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --
  Listener className=org.apache.catalina.core.JasperListener /
  !-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --
  Listener className=org.apache.catalina.mbeans.ServerLifecycleListener /
  Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener /

  !-- Global JNDI resources
   Documentation at /docs/jndi-resources-howto.html
  --
  GlobalNamingResources
!-- Editable user database that can also be used by
 UserDatabaseRealm to authenticate users
--
Resource name=UserDatabase auth=Container
  type=org.apache.catalina.UserDatabase
  description=User database that can be updated and saved
  factory=org.apache.catalina.users.MemoryUserDatabaseFactory
  pathname=conf/tomcat-users.xml /
  /GlobalNamingResources

  !-- A Service is a collection of one or more Connectors that share
   a single Container Note:  A Service is not itself a Container, 
   so you may not define subcomponents such as Valves at this level.
   Documentation at /docs/config/service.html
   --
  Service name=Catalina
  
!--The connectors can use a shared executor, you can define one or more named thread pools--
!--
Executor name=tomcatThreadPool namePrefix=catalina-exec- 
maxThreads=150 minSpareThreads=4/
--


!-- A Connector represents an endpoint by which requests are received
 and responses are returned. Documentation at :
 Java HTTP Connector: /docs/config/http.html (blocking  non-blocking)
 Java AJP  Connector: /docs/config/ajp.html

Slow network with additional Connector (Port) in tomcat

2010-09-01 Thread Yoav Naveh
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!