tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Upgrade to 8.5.8/9
Date Tue, 27 Dec 2016 13:52:55 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Greg,

On 12/27/16 4:58 AM, Greg Huber wrote:
> Since switching to commons-dbcp2 now seems to start OK (so far)
> which prior would have definitely hung.  Fingers crossed.
> 
>> You get complaints about the APR library not being installed?
>> Yeah, just comment-out the APRLifecycleListener in
>> conf/server.xml.
> 
> So using the native connector won't improve the performance?  I use
> https but through Apache.  The docs say:
> 
> These features allows making Tomcat a general purpose webserver,
> will enable much better integration with other native web
> technologies, and overall make Java much more viable as a full
> fledged webserver platform rather than simply a backend focused
> technology.
> 
> So this does not apply when using mod_jk?  It would save having to
> keep compiling the tomcat-native also.

mod_jk doesn't use TLS, and AJP13 expects to use long-lived
connections from the reverse proxies, so keep-alive behavior with
regard to threading isn't really an issue.

So no, I don't believe the use of the native connector will give you
any discernible difference in performance.

- -chris

> On 19 December 2016 at 18:11, Christopher Schultz < 
> chris@christopherschultz.net> wrote:
> 
> Greg,
> 
> On 12/19/16 4:47 AM, Greg Huber wrote:
>>>> I am currently running tomcat 8.0.32 and have tried to
>>>> upgrade to 8.5.8 and 8.5.9 without success.  I use mod_jk to
>>>> connect apache to tomcat running on centos 5.11 with Apache
>>>> 2.2.3.
>>>> 
>>>> I have installed openSSL 1.0.2.j to compile the native 
>>>> tomcat-native-1.2.10 using apr-1.5.2 and
>>>> tomcat-connectors-1.2.42 for the mod_jk.
> 
> If you are using httpd + mod_jk, why are you bothering with APR
> and tcnative on the Tomcat side?
> 
>>>> The problem is that tomcat seems to start but fails sometimes
>>>> to connect correctly to apache and causes apache to hang.  If
>>>> I stop tomcat, apache starts working again.  I have been
>>>> through the logs with little indication of the problem.  If I
>>>> revet back to 8.0.32 everything works OK.
> 
> What if you use the NIO connector instead of APR?
> 
>>>> All I can find is this in the mod_jk.log:
>>>> 
>>>> 
>>>> [Sat Dec 17 06:11:48 2016][3212:47280261211024] [info] 
>>>> init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized [Sat Dec
>>>> 17 06:11:50 2016][3254:47280261211024] [info] 
>>>> jk_open_socket::jk_connect.c (817): connect to
>>>> 127.0.0.1:8009 failed (errno=111) [Sat Dec 17 06:11:50
>>>> 2016][3254:47280261211024] [info]
>>>> ajp_connect_to_endpoint::jk_ajp_common.c (1068): (worker1) 
>>>> Failed opening socket to (127.0.0.1:8009) (errno=111) [Sat
>>>> Dec 17 06:11:50 2016][3254:47280261211024] [error] 
>>>> ajp_send_request::jk_ajp_common.c (1728): (worker1)
>>>> connecting to backend failed. Tomcat is probably not started
>>>> or is listening on the wrong port (errno=111) [Sat Dec 17
>>>> 06:11:50 2016][3254:47280261211024] [info]
>>>> ajp_service::jk_ajp_common.c (2778): (worker1) sending
>>>> request to tomcat failed (recoverable), because of error
>>>> during request sending (attempt=1) [Sat Dec 17 06:11:50
>>>> 2016][3254:47280261211024] [info] 
>>>> jk_open_socket::jk_connect.c (817): connect to
>>>> 127.0.0.1:8009 failed (errno=111) [Sat Dec 17 06:11:50
>>>> 2016][3254:47280261211024] [info]
>>>> ajp_connect_to_endpoint::jk_ajp_common.c (1068): (worker1) 
>>>> Failed opening socket to (127.0.0.1:8009) (errno=111) [Sat
>>>> Dec 17 06:11:50 2016][3254:47280261211024] [error] 
>>>> ajp_send_request::jk_ajp_common.c (1728): (worker1)
>>>> connecting to backend failed. Tomcat is probably not started
>>>> or is listening on the wrong port (errno=111) [Sat Dec 17
>>>> 06:11:50 2016][3254:47280261211024] [info]
>>>> ajp_service::jk_ajp_common.c (2778): (worker1) sending
>>>> request to tomcat failed (recoverable), because of error
>>>> during request sending (attempt=2) [Sat Dec 17 06:11:50
>>>> 2016][3254:47280261211024] [error] 
>>>> ajp_service::jk_ajp_common.c (2799): (worker1) connecting to
>>>> tomcat failed (rc=-3, errors=1, client_errors=0). [Sat Dec 17
>>>> 06:11:50 2016][3254:47280261211024] [info]
>>>> jk_handler::mod_jk.c (2995): Service error=-3 for
>>>> worker=worker1
>>>> 
>>>> Any ideas on what I should check?
> 
> Can you post your <Connector> configuration?
> 
> Any errors in the log files (specifically logs/catalina.out or, if
> you are using jsvc or Windows services,
> stdout.log/stderr.log/etc.)?
> 
> -chris
>> 
>> ---------------------------------------------------------------------
>>
>> 
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>> 
>> 
> 
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYYnI3AAoJEBzwKT+lPKRYRD4P/2lt6SMqbUk4rKnQN7mI648f
zMbpP2UqblFv2b5DWm0hcWgFTrzuuzbMTJRqFDXvMYUYZ43HqYC2m7X/ECwyZSiF
CXL6soNx8vc5lM8daV2nLUAPuZQ23t++uP7hX/bY6CoEGLlioXE2Rpl8+GqjE6Vw
uqu08vCjXLpvHhksvfLYz3DL3Uw1dg/UUmFP/euJfeUXkvEhuow3lca631iz6Xqm
yoKtDsBkAd0vP8BHkECUDAxtBtsGz+k0Tq9VtzBiPkScIok55/wMCvgPtJZViAba
YdW0HOJkXip6Y7dIqBhtfEEeFtdVVgSbXisdn9QDl+QKQAYQQMDQWZs3mzAeLxzi
OI5nOQM2TUvsofLfmwSQNIHTAheqEEehTaZX4xHCj7Wfd8a/vLPS6Y05LWnyxxjK
TNsOluConcYvx/Ni8SfsGp6HHuZ7n3VofI7qnfv9+9IiP0FXmKJmiV9wgK1FgBmc
4uvJOEpElmr/+Oe/Vn+pjvBg2o64fxp3DnC9OiYEe14CzHAsuqLvL1n/DEMsYvqw
046yhO0E2JBBRndQZs7VHqbfJZjORuWLXXQjzT9yJ8228QVunOe9W511IdESI28T
UnMGqp5Evrd7MFfWF1eq0cWoJKlbHEj/TTkh0d3rmyCPddY1gpXP1FcLOc0eMvQ/
OgRN73wShNymbuDbBPYu
=LbJP
-----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