tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: tomcat 7 APR Connector problems
Date Fri, 12 Oct 2012 15:49:50 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrey,

On 10/12/12 11:30 AM, Andrey Timofeyev wrote:
> Hi, everybody,
> 
> There is followen problem with tomcat 7.0.29 (With tomcat 6.0.18
> there is no such problem):
> 
> Any other services on the same machine lost connections with
> remote services, when number of incoming connections to tomcat
> reach pollerSize. (It seems that all file descriptors is used or
> something else)
> 
> As I see in the tomcat 7  latch was added in AprEndpoint, and if 
> connections reach maxLimit Acceptor locked on the latch.
> 
> Here is server configuration: Linux 2.6.34.6-uni-02 #1 SMP Mon Sep
> 19 17:13:09 MSD 2011 x86_64 x86_64 x86_64 GNU/Linux APR:
> libapr1-1.4.6-3.8 kernel.panic = 20 
> net.ipv4.conf.all.accept_redirects = 0 
> net.ipv4.conf.default.accept_redirects = 0 
> net.ipv4.conf.all.rp_filter = 0 net.ipv4.conf.default.rp_filter =
> 0 net.ipv4.icmp_echo_ignore_broadcasts = 1 vm.min_free_kbytes =
> 65536 vm.swappiness = 0 net.core.optmem_max = 16777216 
> net.core.rmem_max = 16777216 net.core.rmem_default = 16777216 
> net.core.wmem_max = 16777216 net.core.wmem_default = 16777216 
> net.ipv4.tcp_rmem = 4096 16777216 16777216 net.ipv4.tcp_wmem = 4096
> 16777216 16777216 net.core.netdev_max_backlog = 300000 
> net.core.somaxconn = 65536 net.ipv4.tcp_max_orphans = 262144 
> net.ipv4.tcp_max_syn_backlog = 65536 net.ipv4.tcp_max_tw_buckets =
> 1048576 net.ipv4.tcp_sack = 1 net.ipv4.tcp_synack_retries = 3 
> net.ipv4.tcp_syncookies = 1 net.ipv4.tcp_syn_retries = 3 
> net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_window_scaling = 1 
> net.ipv4.conf.all.arp_filter = 1 net.ipv4.conf.default.arp_filter =
> 1 net.ipv4.conf.all.arp_ignore = 1 net.ipv4.conf.default.arp_ignore
> = 1 net.ipv4.conf.all.arp_announce = 2 
> net.ipv4.conf.default.arp_announce = 2 
> net.ipv4.neigh.default.gc_thresh1 = 2048 
> net.ipv4.neigh.default.gc_thresh2 = 4096 
> net.ipv4.neigh.default.gc_thresh3 = 8192
> 
> Is it tomcat issue or some misconfiguration?

What about your Tomcat configuration?

Do you get exceptions or apparent deadlock? Can you generate a thread
dump? Are your client connections long-lived? How long? What does
'ulimit -n' tell you?

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB4PB4ACgkQ9CaO5/Lv0PB6owCfdKmTMEEiaZrlEOWwDSn8Zdic
P7MAn0dmd8U6FJMZvWEg89o8wWEuCqJV
=rdPD
-----END PGP SIGNATURE-----

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


Mime
View raw message