You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Greg Huber <gr...@gmail.com> on 2016/12/19 09:47:49 UTC

Upgrade to 8.5.8/9

Hello,

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.

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.


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?

Cheers

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
>Are you sure that your new instance has an adequate >number of threads
available for httpd to proxy to?

How would I check the threads for httpd?  It normally hangs on startup so
there should be enough system threads.  Would a GC be required when the
system has just started?

I have run my startup scripts years so maybe tomcat 8.5.x needs something
extra, memory? (see setenv.sh below)  I have reverted back to 8.0.x and it
starts and runs OK with no issues.

My setup:

workers.properties:

worker.list=worker1
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
worker.worker1.lbfactor=50
worker.worker1.socket_keepalive=1

tomcat.conf

...
JkWorkersFile "/etc/httpd/conf.d/workers.properties"
# Set the log file
JkLogFile "/etc/httpd/logs/mod_jk.log"
JkShmFile "/etc/httpd/logs/jk-runtime-status.log"
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
....
<VirtualHost *:80>
...
JkMount  / worker1
JkMount  /* worker1
</VirtualHost>


setenv.sh :

export CATALINA_OPTS="$CATALINA_OPTS -Xms256m"
export CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"

export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"

export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"

export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"

export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"

export CATALINA_OPTS="$CATALINA_OPTS -server"

export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"


Not sure where these exports came from but they seem to work up to 8.5.x

Cheers Greg.



On 19 December 2016 at 17:55, Coty Sutherland <cs...@redhat.com> wrote:

> Hm, errno=111 is a connection refusal. Are you sure that your new
> instance has an adequate number of threads available for httpd to
> proxy to? Do you see any errors in your tomcat logging? If you do have
> sufficient threads in the pool, then maybe there is something (like GC
> pauses) hanging your requests that wasn't before and therefore
> exhausting the pool causing rejections.
>
> On Mon, Dec 19, 2016 at 4:47 AM, Greg Huber <gr...@gmail.com> wrote:
> > Hello,
> >
> > 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.
> >
> > 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.
> >
> >
> > 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?
> >
> > Cheers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Coty Sutherland <cs...@redhat.com>.
Hm, errno=111 is a connection refusal. Are you sure that your new
instance has an adequate number of threads available for httpd to
proxy to? Do you see any errors in your tomcat logging? If you do have
sufficient threads in the pool, then maybe there is something (like GC
pauses) hanging your requests that wasn't before and therefore
exhausting the pool causing rejections.

On Mon, Dec 19, 2016 at 4:47 AM, Greg Huber <gr...@gmail.com> wrote:
> Hello,
>
> 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.
>
> 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.
>
>
> 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?
>
> Cheers

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

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
OK, will see if I can do the dumps.  Think i did something similar a while
back when tomcat got into a random loop/high cpu a while back.

Cheers Greg.

On 22 December 2016 at 09:17, Mark Thomas <ma...@apache.org> wrote:

> On 22/12/2016 08:55, Greg Huber wrote:
> > I installed exactly the same versions on my newer centos 7 server and it
> > does not lock up.
> >
> > I have seem this problem before as the production box is old and very
> > slow.  There may have been some changes to the connector stuff for a
> > map/list where it is trying to add and remove at the same time causing a
> > dead lock (eg use a CopyOnWriteArrayList etc instead). This would explain
> > why it is erratic and happens on startup (where system is going to be
> slow).
> >
> > Would it be better to log an issue for this?
>
> Unless you can provide reliable steps to reproduce, an issue based on
> the information provided so far is likely to get resolved as invalid.
>
> When the lock up occurs, take 3 thread dumps ~10s apart. That should
> tell you a) any deadlocks, b) what each of the threads is doing and c)
> identify which threads should be moving that aren't.
>
> If you need help analysing the thread dumps, post them (or links to
> them) here.
>
> Mark
>
> >
> > Cheers Greg
> >
> >
> >
> > On 20 December 2016 at 14:10, Christopher Schultz <
> > chris@christopherschultz.net> wrote:
> >
> > Greg,
> >
> > On 12/20/16 3:21 AM, Greg Huber wrote:
> >>>>> If you are using httpd + mod_jk, why are you bothering with APR
> >>>>> and tcnative on the Tomcat side?
> >>>>
> >>>> It complains in the log file so I do what it says.  If I don't need
> >>>> it it saves me having to compile it all the time.
> >
> > You get complaints about the APR library not being installed? Yeah,
> > just comment-out the APRLifecycleListener in conf/server.xml.
> >
> >>>>> What if you use the NIO connector instead of APR?
> >>>>
> >>>> Have always run tomcat with apache and mod_jk has always worked. I
> >>>> could look at NIO if all else fails.
> >
> > No matter what kind of protocol you use (HTTP, AJP13), you can still
> > choose the I/O strategy (APR, NIO, NIO2). The pure-Java blocking I/O
> > connector (BIO) was removed in 8.5.x and 9.0.x, so that's no longer an
> > option.
> >
> >>>>> Can you post your <Connector> configuration?
> >>>>
> >>>> I do not modify anything here.
> >>>>
> >>>> My setup:
> >>>>
> >>>> workers.properties:
> >>>>
> >>>> worker.list=worker1 worker.worker1.type=ajp13
> >>>> worker.worker1.host=localhost worker.worker1.port=8009
> >>>> worker.worker1.lbfactor=50 worker.worker1.socket_keepalive=1
> >>>>
> >>>> tomcat.conf
> >>>>
> >>>> ... JkWorkersFile "/etc/httpd/conf.d/workers.properties" # Set the
> >>>> log file JkLogFile "/etc/httpd/logs/mod_jk.log" JkShmFile
> >>>> "/etc/httpd/logs/jk-runtime-status.log" JkLogLevel info
> >>>> JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" .... <VirtualHost *:80>
> >>>> ... JkMount  / worker1 JkMount  /* worker1 </VirtualHost>
> >
> > That looks okay to me, though it doesn't look like you actually need
> > httpd in the mix, here. I'll just assume that you are fronting Tomcat
> > for a good reason and not "because that's how it's supposed to be done."
> >
> >>>> setenv.sh :
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -Xms256m" export
> >>>> CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"
> >
> > Off-topic hint: if you are going to give your JVM 768M, you may as
> > well do it all at once and set -Xms == -Xmx.
> >
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -server"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
> >>>>
> >>>>
> >>>> Not sure where these exports came from but they seem to work up to
> >>>> 8.5.x
> >
> > They control the JVM, not Tomcat. If you are administering this Tomcat
> > instance, I urge you to learn more about what they do. Mysteries don't
> > help administrators do their jobs.
> >
> >>>> The last start/stop catalina.out :
> >>>>
> >>>> 17-Dec-2016 15:21:51.022 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
> >>>> APR based Apache Tomcat Native library 1.2.10 using APR version
> >>>> 1.5.2. 17-Dec-2016 15:21:51.022 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> >>>> capabilities: IPv6 [true], sendfile [true], accept filters [false],
> >>>> random [true]. 17-Dec-2016 15:21:51.023 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> >>>> APR/OpenSSL configuration: useAprConnector [false], useOpenSSL
> >>>> [true] 17-Dec-2016 15:21:51.036 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.initializeSSL
> >>>> OpenSSL successfully initialized (OpenSSL 1.0.2j  26 Sep 2016)
> >>>> 17-Dec-2016 15:21:52.967 INFO [main]
> >>>> org.apache.coyote.AbstractProtocol.init Initializing
> >>>> ProtocolHandler ["http-nio-8080"] 17-Dec-2016 15:21:53.124 INFO
> >>>> [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
> >>>> Using a shared selector for servlet write/read 17-Dec-2016
> >>>> 15:21:53.160 INFO [main] org.apache.coyote.AbstractProtocol.init
> >>>> Initializing ProtocolHandler ["ajp-nio-8009"]
> >
> > So, you've got an HTTP connector on port 8080 and an AJP connector on
> > port 8009. You aren't using TLS at all, so you can definitely let the
> > APR LifecycleListener go and stop re-compiling libtcnative for each
> > release. It looks like you also aren't using your connector on port
> > 8080, so you can disable that, too. You likely have JVM threads that
> > are sitting idle all the time.
> >
> > Oh, and you're already using NIO. :)
> >
> >>>> 17-Dec-2016 15:23:08.320 INFO [main]
> >>>> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> >>>> [http-nio-8080] 17-Dec-2016 15:23:08.341 INFO [main]
> >>>> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> >>>> [ajp-nio-8009]
> >
> > Looks like these guys started-up okay.
> >
> >>>> 17-Dec-2016 15:23:08.342 INFO [main]
> >>>> org.apache.catalina.startup.Catalina.start Server startup in 75173
> >>>> ms
> >
> > Okay.
> >
> >>>> 17-Dec-2016 15:59:45.589 INFO [Thread-7]
> >>>> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> >>>> ["http-nio-8080"] 17-Dec-2016 15:59:45.805 INFO [Thread-7]
> >>>> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> >>>> ["ajp-nio-8009"]
> >
> > A few minutes later, you stop the server.
> >
> > I don't see any problems, here, except that you are saying you are
> > getting connection failures.
> >
> > After Tomcat is started, can you run this command on the server
> > running both httpd and Tomcat?
> >
> > $ sudo netstat -plan | grep 8009
> >
> > -chris
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
Mark,

Its locked up now and I have the dump but it wont let me email it.  Can I
email the whole file somewhere?

Cheers Greg

On 22 December 2016 at 09:17, Mark Thomas <ma...@apache.org> wrote:

> On 22/12/2016 08:55, Greg Huber wrote:
> > I installed exactly the same versions on my newer centos 7 server and it
> > does not lock up.
> >
> > I have seem this problem before as the production box is old and very
> > slow.  There may have been some changes to the connector stuff for a
> > map/list where it is trying to add and remove at the same time causing a
> > dead lock (eg use a CopyOnWriteArrayList etc instead). This would explain
> > why it is erratic and happens on startup (where system is going to be
> slow).
> >
> > Would it be better to log an issue for this?
>
> Unless you can provide reliable steps to reproduce, an issue based on
> the information provided so far is likely to get resolved as invalid.
>
> When the lock up occurs, take 3 thread dumps ~10s apart. That should
> tell you a) any deadlocks, b) what each of the threads is doing and c)
> identify which threads should be moving that aren't.
>
> If you need help analysing the thread dumps, post them (or links to
> them) here.
>
> Mark
>
> >
> > Cheers Greg
> >
> >
> >
> > On 20 December 2016 at 14:10, Christopher Schultz <
> > chris@christopherschultz.net> wrote:
> >
> > Greg,
> >
> > On 12/20/16 3:21 AM, Greg Huber wrote:
> >>>>> If you are using httpd + mod_jk, why are you bothering with APR
> >>>>> and tcnative on the Tomcat side?
> >>>>
> >>>> It complains in the log file so I do what it says.  If I don't need
> >>>> it it saves me having to compile it all the time.
> >
> > You get complaints about the APR library not being installed? Yeah,
> > just comment-out the APRLifecycleListener in conf/server.xml.
> >
> >>>>> What if you use the NIO connector instead of APR?
> >>>>
> >>>> Have always run tomcat with apache and mod_jk has always worked. I
> >>>> could look at NIO if all else fails.
> >
> > No matter what kind of protocol you use (HTTP, AJP13), you can still
> > choose the I/O strategy (APR, NIO, NIO2). The pure-Java blocking I/O
> > connector (BIO) was removed in 8.5.x and 9.0.x, so that's no longer an
> > option.
> >
> >>>>> Can you post your <Connector> configuration?
> >>>>
> >>>> I do not modify anything here.
> >>>>
> >>>> My setup:
> >>>>
> >>>> workers.properties:
> >>>>
> >>>> worker.list=worker1 worker.worker1.type=ajp13
> >>>> worker.worker1.host=localhost worker.worker1.port=8009
> >>>> worker.worker1.lbfactor=50 worker.worker1.socket_keepalive=1
> >>>>
> >>>> tomcat.conf
> >>>>
> >>>> ... JkWorkersFile "/etc/httpd/conf.d/workers.properties" # Set the
> >>>> log file JkLogFile "/etc/httpd/logs/mod_jk.log" JkShmFile
> >>>> "/etc/httpd/logs/jk-runtime-status.log" JkLogLevel info
> >>>> JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" .... <VirtualHost *:80>
> >>>> ... JkMount  / worker1 JkMount  /* worker1 </VirtualHost>
> >
> > That looks okay to me, though it doesn't look like you actually need
> > httpd in the mix, here. I'll just assume that you are fronting Tomcat
> > for a good reason and not "because that's how it's supposed to be done."
> >
> >>>> setenv.sh :
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -Xms256m" export
> >>>> CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"
> >
> > Off-topic hint: if you are going to give your JVM 768M, you may as
> > well do it all at once and set -Xms == -Xmx.
> >
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -server"
> >>>>
> >>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
> >>>>
> >>>>
> >>>> Not sure where these exports came from but they seem to work up to
> >>>> 8.5.x
> >
> > They control the JVM, not Tomcat. If you are administering this Tomcat
> > instance, I urge you to learn more about what they do. Mysteries don't
> > help administrators do their jobs.
> >
> >>>> The last start/stop catalina.out :
> >>>>
> >>>> 17-Dec-2016 15:21:51.022 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
> >>>> APR based Apache Tomcat Native library 1.2.10 using APR version
> >>>> 1.5.2. 17-Dec-2016 15:21:51.022 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> >>>> capabilities: IPv6 [true], sendfile [true], accept filters [false],
> >>>> random [true]. 17-Dec-2016 15:21:51.023 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> >>>> APR/OpenSSL configuration: useAprConnector [false], useOpenSSL
> >>>> [true] 17-Dec-2016 15:21:51.036 INFO [main]
> >>>> org.apache.catalina.core.AprLifecycleListener.initializeSSL
> >>>> OpenSSL successfully initialized (OpenSSL 1.0.2j  26 Sep 2016)
> >>>> 17-Dec-2016 15:21:52.967 INFO [main]
> >>>> org.apache.coyote.AbstractProtocol.init Initializing
> >>>> ProtocolHandler ["http-nio-8080"] 17-Dec-2016 15:21:53.124 INFO
> >>>> [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
> >>>> Using a shared selector for servlet write/read 17-Dec-2016
> >>>> 15:21:53.160 INFO [main] org.apache.coyote.AbstractProtocol.init
> >>>> Initializing ProtocolHandler ["ajp-nio-8009"]
> >
> > So, you've got an HTTP connector on port 8080 and an AJP connector on
> > port 8009. You aren't using TLS at all, so you can definitely let the
> > APR LifecycleListener go and stop re-compiling libtcnative for each
> > release. It looks like you also aren't using your connector on port
> > 8080, so you can disable that, too. You likely have JVM threads that
> > are sitting idle all the time.
> >
> > Oh, and you're already using NIO. :)
> >
> >>>> 17-Dec-2016 15:23:08.320 INFO [main]
> >>>> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> >>>> [http-nio-8080] 17-Dec-2016 15:23:08.341 INFO [main]
> >>>> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> >>>> [ajp-nio-8009]
> >
> > Looks like these guys started-up okay.
> >
> >>>> 17-Dec-2016 15:23:08.342 INFO [main]
> >>>> org.apache.catalina.startup.Catalina.start Server startup in 75173
> >>>> ms
> >
> > Okay.
> >
> >>>> 17-Dec-2016 15:59:45.589 INFO [Thread-7]
> >>>> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> >>>> ["http-nio-8080"] 17-Dec-2016 15:59:45.805 INFO [Thread-7]
> >>>> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> >>>> ["ajp-nio-8009"]
> >
> > A few minutes later, you stop the server.
> >
> > I don't see any problems, here, except that you are saying you are
> > getting connection failures.
> >
> > After Tomcat is started, can you run this command on the server
> > running both httpd and Tomcat?
> >
> > $ sudo netstat -plan | grep 8009
> >
> > -chris
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Mark Thomas <ma...@apache.org>.
On 22/12/2016 08:55, Greg Huber wrote:
> I installed exactly the same versions on my newer centos 7 server and it
> does not lock up.
> 
> I have seem this problem before as the production box is old and very
> slow.  There may have been some changes to the connector stuff for a
> map/list where it is trying to add and remove at the same time causing a
> dead lock (eg use a CopyOnWriteArrayList etc instead). This would explain
> why it is erratic and happens on startup (where system is going to be slow).
> 
> Would it be better to log an issue for this?

Unless you can provide reliable steps to reproduce, an issue based on
the information provided so far is likely to get resolved as invalid.

When the lock up occurs, take 3 thread dumps ~10s apart. That should
tell you a) any deadlocks, b) what each of the threads is doing and c)
identify which threads should be moving that aren't.

If you need help analysing the thread dumps, post them (or links to
them) here.

Mark

> 
> Cheers Greg
> 
> 
> 
> On 20 December 2016 at 14:10, Christopher Schultz <
> chris@christopherschultz.net> wrote:
> 
> Greg,
> 
> On 12/20/16 3:21 AM, Greg Huber wrote:
>>>>> If you are using httpd + mod_jk, why are you bothering with APR
>>>>> and tcnative on the Tomcat side?
>>>>
>>>> It complains in the log file so I do what it says.  If I don't need
>>>> it it saves me having to compile it all the time.
> 
> You get complaints about the APR library not being installed? Yeah,
> just comment-out the APRLifecycleListener in conf/server.xml.
> 
>>>>> What if you use the NIO connector instead of APR?
>>>>
>>>> Have always run tomcat with apache and mod_jk has always worked. I
>>>> could look at NIO if all else fails.
> 
> No matter what kind of protocol you use (HTTP, AJP13), you can still
> choose the I/O strategy (APR, NIO, NIO2). The pure-Java blocking I/O
> connector (BIO) was removed in 8.5.x and 9.0.x, so that's no longer an
> option.
> 
>>>>> Can you post your <Connector> configuration?
>>>>
>>>> I do not modify anything here.
>>>>
>>>> My setup:
>>>>
>>>> workers.properties:
>>>>
>>>> worker.list=worker1 worker.worker1.type=ajp13
>>>> worker.worker1.host=localhost worker.worker1.port=8009
>>>> worker.worker1.lbfactor=50 worker.worker1.socket_keepalive=1
>>>>
>>>> tomcat.conf
>>>>
>>>> ... JkWorkersFile "/etc/httpd/conf.d/workers.properties" # Set the
>>>> log file JkLogFile "/etc/httpd/logs/mod_jk.log" JkShmFile
>>>> "/etc/httpd/logs/jk-runtime-status.log" JkLogLevel info
>>>> JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" .... <VirtualHost *:80>
>>>> ... JkMount  / worker1 JkMount  /* worker1 </VirtualHost>
> 
> That looks okay to me, though it doesn't look like you actually need
> httpd in the mix, here. I'll just assume that you are fronting Tomcat
> for a good reason and not "because that's how it's supposed to be done."
> 
>>>> setenv.sh :
>>>>
>>>> export CATALINA_OPTS="$CATALINA_OPTS -Xms256m" export
>>>> CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"
> 
> Off-topic hint: if you are going to give your JVM 768M, you may as
> well do it all at once and set -Xms == -Xmx.
> 
>>>> export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"
>>>>
>>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"
>>>>
>>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"
>>>>
>>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"
>>>>
>>>> export CATALINA_OPTS="$CATALINA_OPTS -server"
>>>>
>>>> export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
>>>>
>>>>
>>>> Not sure where these exports came from but they seem to work up to
>>>> 8.5.x
> 
> They control the JVM, not Tomcat. If you are administering this Tomcat
> instance, I urge you to learn more about what they do. Mysteries don't
> help administrators do their jobs.
> 
>>>> The last start/stop catalina.out :
>>>>
>>>> 17-Dec-2016 15:21:51.022 INFO [main]
>>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
>>>> APR based Apache Tomcat Native library 1.2.10 using APR version
>>>> 1.5.2. 17-Dec-2016 15:21:51.022 INFO [main]
>>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
>>>> capabilities: IPv6 [true], sendfile [true], accept filters [false],
>>>> random [true]. 17-Dec-2016 15:21:51.023 INFO [main]
>>>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
>>>> APR/OpenSSL configuration: useAprConnector [false], useOpenSSL
>>>> [true] 17-Dec-2016 15:21:51.036 INFO [main]
>>>> org.apache.catalina.core.AprLifecycleListener.initializeSSL
>>>> OpenSSL successfully initialized (OpenSSL 1.0.2j  26 Sep 2016)
>>>> 17-Dec-2016 15:21:52.967 INFO [main]
>>>> org.apache.coyote.AbstractProtocol.init Initializing
>>>> ProtocolHandler ["http-nio-8080"] 17-Dec-2016 15:21:53.124 INFO
>>>> [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
>>>> Using a shared selector for servlet write/read 17-Dec-2016
>>>> 15:21:53.160 INFO [main] org.apache.coyote.AbstractProtocol.init
>>>> Initializing ProtocolHandler ["ajp-nio-8009"]
> 
> So, you've got an HTTP connector on port 8080 and an AJP connector on
> port 8009. You aren't using TLS at all, so you can definitely let the
> APR LifecycleListener go and stop re-compiling libtcnative for each
> release. It looks like you also aren't using your connector on port
> 8080, so you can disable that, too. You likely have JVM threads that
> are sitting idle all the time.
> 
> Oh, and you're already using NIO. :)
> 
>>>> 17-Dec-2016 15:23:08.320 INFO [main]
>>>> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
>>>> [http-nio-8080] 17-Dec-2016 15:23:08.341 INFO [main]
>>>> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
>>>> [ajp-nio-8009]
> 
> Looks like these guys started-up okay.
> 
>>>> 17-Dec-2016 15:23:08.342 INFO [main]
>>>> org.apache.catalina.startup.Catalina.start Server startup in 75173
>>>> ms
> 
> Okay.
> 
>>>> 17-Dec-2016 15:59:45.589 INFO [Thread-7]
>>>> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
>>>> ["http-nio-8080"] 17-Dec-2016 15:59:45.805 INFO [Thread-7]
>>>> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
>>>> ["ajp-nio-8009"]
> 
> A few minutes later, you stop the server.
> 
> I don't see any problems, here, except that you are saying you are
> getting connection failures.
> 
> After Tomcat is started, can you run this command on the server
> running both httpd and Tomcat?
> 
> $ sudo netstat -plan | grep 8009
> 
> -chris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
> 


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

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
I installed exactly the same versions on my newer centos 7 server and it
does not lock up.

I have seem this problem before as the production box is old and very
slow.  There may have been some changes to the connector stuff for a
map/list where it is trying to add and remove at the same time causing a
dead lock (eg use a CopyOnWriteArrayList etc instead). This would explain
why it is erratic and happens on startup (where system is going to be slow).

Would it be better to log an issue for this?

Cheers Greg



On 20 December 2016 at 14:10, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Greg,
>
> On 12/20/16 3:21 AM, Greg Huber wrote:
> >> If you are using httpd + mod_jk, why are you bothering with APR
> >> and tcnative on the Tomcat side?
> >
> > It complains in the log file so I do what it says.  If I don't need
> > it it saves me having to compile it all the time.
>
> You get complaints about the APR library not being installed? Yeah,
> just comment-out the APRLifecycleListener in conf/server.xml.
>
> >> What if you use the NIO connector instead of APR?
> >
> > Have always run tomcat with apache and mod_jk has always worked. I
> > could look at NIO if all else fails.
>
> No matter what kind of protocol you use (HTTP, AJP13), you can still
> choose the I/O strategy (APR, NIO, NIO2). The pure-Java blocking I/O
> connector (BIO) was removed in 8.5.x and 9.0.x, so that's no longer an
> option.
>
> >> Can you post your <Connector> configuration?
> >
> > I do not modify anything here.
> >
> > My setup:
> >
> > workers.properties:
> >
> > worker.list=worker1 worker.worker1.type=ajp13
> > worker.worker1.host=localhost worker.worker1.port=8009
> > worker.worker1.lbfactor=50 worker.worker1.socket_keepalive=1
> >
> > tomcat.conf
> >
> > ... JkWorkersFile "/etc/httpd/conf.d/workers.properties" # Set the
> > log file JkLogFile "/etc/httpd/logs/mod_jk.log" JkShmFile
> > "/etc/httpd/logs/jk-runtime-status.log" JkLogLevel info
> > JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" .... <VirtualHost *:80>
> > ... JkMount  / worker1 JkMount  /* worker1 </VirtualHost>
>
> That looks okay to me, though it doesn't look like you actually need
> httpd in the mix, here. I'll just assume that you are fronting Tomcat
> for a good reason and not "because that's how it's supposed to be done."
>
> > setenv.sh :
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -Xms256m" export
> > CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"
>
> Off-topic hint: if you are going to give your JVM 768M, you may as
> well do it all at once and set -Xms == -Xmx.
>
> > export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -server"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
> >
> >
> > Not sure where these exports came from but they seem to work up to
> > 8.5.x
>
> They control the JVM, not Tomcat. If you are administering this Tomcat
> instance, I urge you to learn more about what they do. Mysteries don't
> help administrators do their jobs.
>
> > The last start/stop catalina.out :
> >
> > 17-Dec-2016 15:21:51.022 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
> > APR based Apache Tomcat Native library 1.2.10 using APR version
> > 1.5.2. 17-Dec-2016 15:21:51.022 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> > capabilities: IPv6 [true], sendfile [true], accept filters [false],
> > random [true]. 17-Dec-2016 15:21:51.023 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> > APR/OpenSSL configuration: useAprConnector [false], useOpenSSL
> > [true] 17-Dec-2016 15:21:51.036 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.initializeSSL
> > OpenSSL successfully initialized (OpenSSL 1.0.2j  26 Sep 2016)
> > 17-Dec-2016 15:21:52.967 INFO [main]
> > org.apache.coyote.AbstractProtocol.init Initializing
> > ProtocolHandler ["http-nio-8080"] 17-Dec-2016 15:21:53.124 INFO
> > [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
> > Using a shared selector for servlet write/read 17-Dec-2016
> > 15:21:53.160 INFO [main] org.apache.coyote.AbstractProtocol.init
> > Initializing ProtocolHandler ["ajp-nio-8009"]
>
> So, you've got an HTTP connector on port 8080 and an AJP connector on
> port 8009. You aren't using TLS at all, so you can definitely let the
> APR LifecycleListener go and stop re-compiling libtcnative for each
> release. It looks like you also aren't using your connector on port
> 8080, so you can disable that, too. You likely have JVM threads that
> are sitting idle all the time.
>
> Oh, and you're already using NIO. :)
>
> > 17-Dec-2016 15:23:08.320 INFO [main]
> > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> > [http-nio-8080] 17-Dec-2016 15:23:08.341 INFO [main]
> > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> > [ajp-nio-8009]
>
> Looks like these guys started-up okay.
>
> > 17-Dec-2016 15:23:08.342 INFO [main]
> > org.apache.catalina.startup.Catalina.start Server startup in 75173
> > ms
>
> Okay.
>
> > 17-Dec-2016 15:59:45.589 INFO [Thread-7]
> > org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> > ["http-nio-8080"] 17-Dec-2016 15:59:45.805 INFO [Thread-7]
> > org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> > ["ajp-nio-8009"]
>
> A few minutes later, you stop the server.
>
> I don't see any problems, here, except that you are saying you are
> getting connection failures.
>
> After Tomcat is started, can you run this command on the server
> running both httpd and Tomcat?
>
> $ sudo netstat -plan | grep 8009
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYWTvjAAoJEBzwKT+lPKRYTP8P/Rw7FhZ6mQEm8JRibfUdEWA3
> qg9gD+2ueIFXkvxfrhIQy1/xfPpmnDIB+X89pSZo+gq9hk9uxPJgneZKGW/K4qD8
> sICqi/S6mcEQOGHUYHwdTE9p0lFQwoijZ6O9ViWqcbgTndoYuDCWSNp+3ZMOCeYS
> IFOZbeUlJyLtMOv1aGnP3LSpi38yHUTLRhBd2/kf5C47+C8iwggN1z6yIRS+vIVb
> odzI1RR5hPxG4Sy6VNRusiyPowBsMtQ7U0EUdU2abW9X8FD0h8XYx6Qg1NCRUfIU
> R5OM0SFDu52zbNy1fweZ5P3yW7sOHQ6ocVnrENPoCjJnW05rR8PoGmtKEqDMZJf4
> mgbNnB2zb/Eu+RfQaeqjnOB7ch0BxHJE78GfRQSPJ78F+DVHxFCpYNuSA5R+16vE
> aj/sQMPFf/G2r1GDqgGykxVkkQqBBfPcpGDVbVIHQ2sUiNwW4zya1o3jV2lHNjFd
> tqnDZg1UWuljBLL/Cm273ueja0t50KCLAr88ZsmFiVCUOktmgjBYzT+pRDCkeLha
> s8c2Zc1dRr3Qh9ve/LBwVydMO8ZtFw2fGAejSvhhukXbuUNPeMw1PN4pSPRQpgbL
> NHna5qiziTzXn8yrfJihM2fgontqqP5MtPo0v6JbRhyAcgy8boCz+0llnjxVxBfN
> eLQxC/coibB4KP0ZhsH5
> =LR38
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
Chris,

>After Tomcat is started, can you run this command on >the server running
both httpd and Tomcat?

>$ sudo netstat -plan | grep 8009

The problem is my prod server (centos 5), so I will switch back to 8.5.9
and when it hangs I can run the command.  Also I do have a backup server
(centos 7) which I will also update to 8.5.9 and see if I get the same
issue which will allow more testing also.


Cheers. Greg

On 20 December 2016 at 14:10, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Greg,
>
> On 12/20/16 3:21 AM, Greg Huber wrote:
> >> If you are using httpd + mod_jk, why are you bothering with APR
> >> and tcnative on the Tomcat side?
> >
> > It complains in the log file so I do what it says.  If I don't need
> > it it saves me having to compile it all the time.
>
> You get complaints about the APR library not being installed? Yeah,
> just comment-out the APRLifecycleListener in conf/server.xml.
>
> >> What if you use the NIO connector instead of APR?
> >
> > Have always run tomcat with apache and mod_jk has always worked. I
> > could look at NIO if all else fails.
>
> No matter what kind of protocol you use (HTTP, AJP13), you can still
> choose the I/O strategy (APR, NIO, NIO2). The pure-Java blocking I/O
> connector (BIO) was removed in 8.5.x and 9.0.x, so that's no longer an
> option.
>
> >> Can you post your <Connector> configuration?
> >
> > I do not modify anything here.
> >
> > My setup:
> >
> > workers.properties:
> >
> > worker.list=worker1 worker.worker1.type=ajp13
> > worker.worker1.host=localhost worker.worker1.port=8009
> > worker.worker1.lbfactor=50 worker.worker1.socket_keepalive=1
> >
> > tomcat.conf
> >
> > ... JkWorkersFile "/etc/httpd/conf.d/workers.properties" # Set the
> > log file JkLogFile "/etc/httpd/logs/mod_jk.log" JkShmFile
> > "/etc/httpd/logs/jk-runtime-status.log" JkLogLevel info
> > JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" .... <VirtualHost *:80>
> > ... JkMount  / worker1 JkMount  /* worker1 </VirtualHost>
>
> That looks okay to me, though it doesn't look like you actually need
> httpd in the mix, here. I'll just assume that you are fronting Tomcat
> for a good reason and not "because that's how it's supposed to be done."
>
> > setenv.sh :
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -Xms256m" export
> > CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"
>
> Off-topic hint: if you are going to give your JVM 768M, you may as
> well do it all at once and set -Xms == -Xmx.
>
> > export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -server"
> >
> > export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
> >
> >
> > Not sure where these exports came from but they seem to work up to
> > 8.5.x
>
> They control the JVM, not Tomcat. If you are administering this Tomcat
> instance, I urge you to learn more about what they do. Mysteries don't
> help administrators do their jobs.
>
> > The last start/stop catalina.out :
> >
> > 17-Dec-2016 15:21:51.022 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
> > APR based Apache Tomcat Native library 1.2.10 using APR version
> > 1.5.2. 17-Dec-2016 15:21:51.022 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
> > capabilities: IPv6 [true], sendfile [true], accept filters [false],
> > random [true]. 17-Dec-2016 15:21:51.023 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> > APR/OpenSSL configuration: useAprConnector [false], useOpenSSL
> > [true] 17-Dec-2016 15:21:51.036 INFO [main]
> > org.apache.catalina.core.AprLifecycleListener.initializeSSL
> > OpenSSL successfully initialized (OpenSSL 1.0.2j  26 Sep 2016)
> > 17-Dec-2016 15:21:52.967 INFO [main]
> > org.apache.coyote.AbstractProtocol.init Initializing
> > ProtocolHandler ["http-nio-8080"] 17-Dec-2016 15:21:53.124 INFO
> > [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
> > Using a shared selector for servlet write/read 17-Dec-2016
> > 15:21:53.160 INFO [main] org.apache.coyote.AbstractProtocol.init
> > Initializing ProtocolHandler ["ajp-nio-8009"]
>
> So, you've got an HTTP connector on port 8080 and an AJP connector on
> port 8009. You aren't using TLS at all, so you can definitely let the
> APR LifecycleListener go and stop re-compiling libtcnative for each
> release. It looks like you also aren't using your connector on port
> 8080, so you can disable that, too. You likely have JVM threads that
> are sitting idle all the time.
>
> Oh, and you're already using NIO. :)
>
> > 17-Dec-2016 15:23:08.320 INFO [main]
> > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> > [http-nio-8080] 17-Dec-2016 15:23:08.341 INFO [main]
> > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
> > [ajp-nio-8009]
>
> Looks like these guys started-up okay.
>
> > 17-Dec-2016 15:23:08.342 INFO [main]
> > org.apache.catalina.startup.Catalina.start Server startup in 75173
> > ms
>
> Okay.
>
> > 17-Dec-2016 15:59:45.589 INFO [Thread-7]
> > org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> > ["http-nio-8080"] 17-Dec-2016 15:59:45.805 INFO [Thread-7]
> > org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
> > ["ajp-nio-8009"]
>
> A few minutes later, you stop the server.
>
> I don't see any problems, here, except that you are saying you are
> getting connection failures.
>
> After Tomcat is started, can you run this command on the server
> running both httpd and Tomcat?
>
> $ sudo netstat -plan | grep 8009
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYWTvjAAoJEBzwKT+lPKRYTP8P/Rw7FhZ6mQEm8JRibfUdEWA3
> qg9gD+2ueIFXkvxfrhIQy1/xfPpmnDIB+X89pSZo+gq9hk9uxPJgneZKGW/K4qD8
> sICqi/S6mcEQOGHUYHwdTE9p0lFQwoijZ6O9ViWqcbgTndoYuDCWSNp+3ZMOCeYS
> IFOZbeUlJyLtMOv1aGnP3LSpi38yHUTLRhBd2/kf5C47+C8iwggN1z6yIRS+vIVb
> odzI1RR5hPxG4Sy6VNRusiyPowBsMtQ7U0EUdU2abW9X8FD0h8XYx6Qg1NCRUfIU
> R5OM0SFDu52zbNy1fweZ5P3yW7sOHQ6ocVnrENPoCjJnW05rR8PoGmtKEqDMZJf4
> mgbNnB2zb/Eu+RfQaeqjnOB7ch0BxHJE78GfRQSPJ78F+DVHxFCpYNuSA5R+16vE
> aj/sQMPFf/G2r1GDqgGykxVkkQqBBfPcpGDVbVIHQ2sUiNwW4zya1o3jV2lHNjFd
> tqnDZg1UWuljBLL/Cm273ueja0t50KCLAr88ZsmFiVCUOktmgjBYzT+pRDCkeLha
> s8c2Zc1dRr3Qh9ve/LBwVydMO8ZtFw2fGAejSvhhukXbuUNPeMw1PN4pSPRQpgbL
> NHna5qiziTzXn8yrfJihM2fgontqqP5MtPo0v6JbRhyAcgy8boCz+0llnjxVxBfN
> eLQxC/coibB4KP0ZhsH5
> =LR38
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Greg,

On 12/20/16 3:21 AM, Greg Huber wrote:
>> If you are using httpd + mod_jk, why are you bothering with APR
>> and tcnative on the Tomcat side?
> 
> It complains in the log file so I do what it says.  If I don't need
> it it saves me having to compile it all the time.

You get complaints about the APR library not being installed? Yeah,
just comment-out the APRLifecycleListener in conf/server.xml.

>> What if you use the NIO connector instead of APR?
> 
> Have always run tomcat with apache and mod_jk has always worked. I
> could look at NIO if all else fails.

No matter what kind of protocol you use (HTTP, AJP13), you can still
choose the I/O strategy (APR, NIO, NIO2). The pure-Java blocking I/O
connector (BIO) was removed in 8.5.x and 9.0.x, so that's no longer an
option.

>> Can you post your <Connector> configuration?
> 
> I do not modify anything here.
> 
> My setup:
> 
> workers.properties:
> 
> worker.list=worker1 worker.worker1.type=ajp13 
> worker.worker1.host=localhost worker.worker1.port=8009 
> worker.worker1.lbfactor=50 worker.worker1.socket_keepalive=1
> 
> tomcat.conf
> 
> ... JkWorkersFile "/etc/httpd/conf.d/workers.properties" # Set the
> log file JkLogFile "/etc/httpd/logs/mod_jk.log" JkShmFile
> "/etc/httpd/logs/jk-runtime-status.log" JkLogLevel info 
> JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" .... <VirtualHost *:80> 
> ... JkMount  / worker1 JkMount  /* worker1 </VirtualHost>

That looks okay to me, though it doesn't look like you actually need
httpd in the mix, here. I'll just assume that you are fronting Tomcat
for a good reason and not "because that's how it's supposed to be done."

> setenv.sh :
> 
> export CATALINA_OPTS="$CATALINA_OPTS -Xms256m" export
> CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"

Off-topic hint: if you are going to give your JVM 768M, you may as
well do it all at once and set -Xms == -Xmx.

> export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"
> 
> export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"
> 
> export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"
> 
> export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"
> 
> export CATALINA_OPTS="$CATALINA_OPTS -server"
> 
> export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
> 
> 
> Not sure where these exports came from but they seem to work up to
> 8.5.x

They control the JVM, not Tomcat. If you are administering this Tomcat
instance, I urge you to learn more about what they do. Mysteries don't
help administrators do their jobs.

> The last start/stop catalina.out :
> 
> 17-Dec-2016 15:21:51.022 INFO [main] 
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded
> APR based Apache Tomcat Native library 1.2.10 using APR version
> 1.5.2. 17-Dec-2016 15:21:51.022 INFO [main] 
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR 
> capabilities: IPv6 [true], sendfile [true], accept filters [false],
> random [true]. 17-Dec-2016 15:21:51.023 INFO [main] 
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
> APR/OpenSSL configuration: useAprConnector [false], useOpenSSL
> [true] 17-Dec-2016 15:21:51.036 INFO [main] 
> org.apache.catalina.core.AprLifecycleListener.initializeSSL
> OpenSSL successfully initialized (OpenSSL 1.0.2j  26 Sep 2016) 
> 17-Dec-2016 15:21:52.967 INFO [main] 
> org.apache.coyote.AbstractProtocol.init Initializing
> ProtocolHandler ["http-nio-8080"] 17-Dec-2016 15:21:53.124 INFO
> [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
> Using a shared selector for servlet write/read 17-Dec-2016
> 15:21:53.160 INFO [main] org.apache.coyote.AbstractProtocol.init
> Initializing ProtocolHandler ["ajp-nio-8009"]

So, you've got an HTTP connector on port 8080 and an AJP connector on
port 8009. You aren't using TLS at all, so you can definitely let the
APR LifecycleListener go and stop re-compiling libtcnative for each
release. It looks like you also aren't using your connector on port
8080, so you can disable that, too. You likely have JVM threads that
are sitting idle all the time.

Oh, and you're already using NIO. :)

> 17-Dec-2016 15:23:08.320 INFO [main] 
> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
> [http-nio-8080] 17-Dec-2016 15:23:08.341 INFO [main] 
> org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler 
> [ajp-nio-8009]

Looks like these guys started-up okay.

> 17-Dec-2016 15:23:08.342 INFO [main] 
> org.apache.catalina.startup.Catalina.start Server startup in 75173
> ms

Okay.

> 17-Dec-2016 15:59:45.589 INFO [Thread-7] 
> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler 
> ["http-nio-8080"] 17-Dec-2016 15:59:45.805 INFO [Thread-7] 
> org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler 
> ["ajp-nio-8009"]

A few minutes later, you stop the server.

I don't see any problems, here, except that you are saying you are
getting connection failures.

After Tomcat is started, can you run this command on the server
running both httpd and Tomcat?

$ sudo netstat -plan | grep 8009

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYWTvjAAoJEBzwKT+lPKRYTP8P/Rw7FhZ6mQEm8JRibfUdEWA3
qg9gD+2ueIFXkvxfrhIQy1/xfPpmnDIB+X89pSZo+gq9hk9uxPJgneZKGW/K4qD8
sICqi/S6mcEQOGHUYHwdTE9p0lFQwoijZ6O9ViWqcbgTndoYuDCWSNp+3ZMOCeYS
IFOZbeUlJyLtMOv1aGnP3LSpi38yHUTLRhBd2/kf5C47+C8iwggN1z6yIRS+vIVb
odzI1RR5hPxG4Sy6VNRusiyPowBsMtQ7U0EUdU2abW9X8FD0h8XYx6Qg1NCRUfIU
R5OM0SFDu52zbNy1fweZ5P3yW7sOHQ6ocVnrENPoCjJnW05rR8PoGmtKEqDMZJf4
mgbNnB2zb/Eu+RfQaeqjnOB7ch0BxHJE78GfRQSPJ78F+DVHxFCpYNuSA5R+16vE
aj/sQMPFf/G2r1GDqgGykxVkkQqBBfPcpGDVbVIHQ2sUiNwW4zya1o3jV2lHNjFd
tqnDZg1UWuljBLL/Cm273ueja0t50KCLAr88ZsmFiVCUOktmgjBYzT+pRDCkeLha
s8c2Zc1dRr3Qh9ve/LBwVydMO8ZtFw2fGAejSvhhukXbuUNPeMw1PN4pSPRQpgbL
NHna5qiziTzXn8yrfJihM2fgontqqP5MtPo0v6JbRhyAcgy8boCz+0llnjxVxBfN
eLQxC/coibB4KP0ZhsH5
=LR38
-----END PGP SIGNATURE-----

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

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
> If you are using httpd + mod_jk, why are you
> bothering with APR and tcnative on the Tomcat
> side?

It complains in the log file so I do what it says.  If I don't need it it
saves me having to compile it all the time.

> What if you use the NIO connector instead of APR?

Have always run tomcat with apache and mod_jk has always worked. I could
look at NIO if all else fails.

> Can you post your <Connector> configuration?

I do not modify anything here.

My setup:

workers.properties:

worker.list=worker1
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
worker.worker1.lbfactor=50
worker.worker1.socket_keepalive=1

tomcat.conf

...
JkWorkersFile "/etc/httpd/conf.d/workers.properties"
# Set the log file
JkLogFile "/etc/httpd/logs/mod_jk.log"
JkShmFile "/etc/httpd/logs/jk-runtime-status.log"
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
....
<VirtualHost *:80>
...
JkMount  / worker1
JkMount  /* worker1
</VirtualHost>


setenv.sh :

export CATALINA_OPTS="$CATALINA_OPTS -Xms256m"
export CATALINA_OPTS="$CATALINA_OPTS -Xmx768m"

export CATALINA_OPTS="$CATALINA_OPTS -Xss256k"

export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseParallelGC"

export CATALINA_OPTS="$CATALINA_OPTS -XX:MaxGCPauseMillis=1500"

export CATALINA_OPTS="$CATALINA_OPTS -XX:GCTimeRatio=9"

export CATALINA_OPTS="$CATALINA_OPTS -server"

export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"


Not sure where these exports came from but they seem to work up to 8.5.x


The last start/stop catalina.out :

17-Dec-2016 15:21:51.007 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server
version:        Apache Tomcat/8.5.8
17-Dec-2016 15:21:51.012 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server
built:          Nov 3 2016 21:14:13 UTC
17-Dec-2016 15:21:51.012 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server
number:         8.5.8.0
17-Dec-2016 15:21:51.012 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS
Name:               Linux
17-Dec-2016 15:21:51.013 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS
Version:            2.6.18-416.el5
17-Dec-2016 15:21:51.013 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log
Architecture:          amd64
17-Dec-2016 15:21:51.013 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Java
Home:             /opt/oraclejava1.8/jdk1.8.0_40/jre
17-Dec-2016 15:21:51.014 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM
Version:           1.8.0_40-b26
17-Dec-2016 15:21:51.014 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM
Vendor:            Oracle Corporation
17-Dec-2016 15:21:51.014 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log
CATALINA_BASE:         /opt/apache-tomcat/apache-tomcat-8.5.8
17-Dec-2016 15:21:51.015 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log
CATALINA_HOME:         /opt/apache-tomcat/apache-tomcat-8.5.8
17-Dec-2016 15:21:51.017 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Devents.nodename=VM0
17-Dec-2016 15:21:51.017 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Devents.activemq.portZ=61617
17-Dec-2016 15:21:51.018 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Duser.timezone=Europe/London
17-Dec-2016 15:21:51.018 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
17-Dec-2016 15:21:51.018 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument:
-Djava.util.logging.config.file=/opt/apache-tomcat/apache-tomcat-8.5.8/conf/logging.properties
17-Dec-2016 15:21:51.019 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Xms256m
17-Dec-2016 15:21:51.019 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Xmx768m
17-Dec-2016 15:21:51.019 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Xss256k
17-Dec-2016 15:21:51.020 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -XX:+UseParallelGC
17-Dec-2016 15:21:51.020 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -XX:MaxGCPauseMillis=1500
17-Dec-2016 15:21:51.020 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -XX:GCTimeRatio=9
17-Dec-2016 15:21:51.021 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -XX:+DisableExplicitGC
17-Dec-2016 15:21:51.021 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.endorsed.dirs=
17-Dec-2016 15:21:51.021 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.base=/opt/apache-tomcat/apache-tomcat-8.5.8
17-Dec-2016 15:21:51.022 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.home=/opt/apache-tomcat/apache-tomcat-8.5.8
17-Dec-2016 15:21:51.022 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.io.tmpdir=/opt/apache-tomcat/apache-tomcat-8.5.8/temp
17-Dec-2016 15:21:51.022 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR
based Apache Tomcat Native library 1.2.10 using APR version 1.5.2.
17-Dec-2016 15:21:51.022 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR
capabilities: IPv6 [true], sendfile [true], accept filters [false], random
[true].
17-Dec-2016 15:21:51.023 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL
configuration: useAprConnector [false], useOpenSSL [true]
17-Dec-2016 15:21:51.036 INFO [main]
org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL
successfully initialized (OpenSSL 1.0.2j  26 Sep 2016)
17-Dec-2016 15:21:52.967 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
["http-nio-8080"]
17-Dec-2016 15:21:53.124 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read
17-Dec-2016 15:21:53.160 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
["ajp-nio-8009"]
17-Dec-2016 15:21:53.167 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read
17-Dec-2016 15:21:53.168 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in 4843
ms
17-Dec-2016 15:21:53.439 INFO [main]
org.apache.catalina.core.StandardService.startInternal Starting service
Catalina
17-Dec-2016 15:21:53.439 INFO [main]
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
Engine: Apache Tomcat/8.5.8
17-Dec-2016 15:21:53.617 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDescriptor Deploying
configuration descriptor
/opt/apache-tomcat/apache-tomcat-8.5.8/conf/Catalina/localhost/ROOT.xml
17-Dec-2016 15:22:29.227 INFO [localhost-startStop-1]
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned
for TLDs yet contained no TLDs. Enable debug logging for this logger for a
complete list of JARs that were scanned but no TLDs were found in them.
Skipping unneeded JARs during scanning can improve startup time and JSP
compilation time.
17-Dec-2016 15:23:08.302 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of
configuration descriptor
/opt/apache-tomcat/apache-tomcat-8.5.8/conf/Catalina/localhost/ROOT.xml has
finished in 74,682 ms
17-Dec-2016 15:23:08.320 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
[http-nio-8080]
17-Dec-2016 15:23:08.341 INFO [main]
org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler
[ajp-nio-8009]
17-Dec-2016 15:23:08.342 INFO [main]
org.apache.catalina.startup.Catalina.start Server startup in 75173 ms
17-Dec-2016 15:59:45.589 INFO [Thread-7]
org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
["http-nio-8080"]
17-Dec-2016 15:59:45.805 INFO [Thread-7]
org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
["ajp-nio-8009"]
17-Dec-2016 15:59:45.869 INFO [Thread-7]
org.apache.catalina.core.StandardService.stopInternal Stopping service
Catalina
17-Dec-2016 15:59:52.152 INFO [Thread-7]
org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler
["http-nio-8080"]
17-Dec-2016 15:59:52.401 INFO [Thread-7]
org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler
["ajp-nio-8009"]
17-Dec-2016 15:59:52.536 INFO [Thread-7]
org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler
["http-nio-8080"]
17-Dec-2016 15:59:52.605 INFO [Thread-7]
org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler
["ajp-nio-8009"]


Cheers Greg


On 19 December 2016 at 18:11, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> 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
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYWCLGAAoJEBzwKT+lPKRYzqcP/R34lxIW90ZPn7SQ5SBsbKN8
> rvYD+4k7a3EGEnPUhfJaajOMbpTXdPTHyltHOID9CpRRFIGrb+/kcKmaLbllYIqq
> NUDvWSDUHK0yELaSjb7+Y980mygqXV3j8wAardcEnZ/wG143ZZozhpQtKjhpLmsb
> XMe0HiC9/4TeqCtyZ5IWRdq/UOotnU0m1QMjgGYQPztGwQlfvNYDZ//8apiYkCKY
> qUoblyNM1RiH4H6tiX+7ZEfk3exvArw84adcWULYiQNpHMwvsRlfMi1aq8Xcty5+
> xhB4SitKoEB6CY/oLwRjWYAUsQIov2trGoqbhxIiQcNpHxoKslLabvzdjmjMPMj0
> kbMiGpOFfK4ULqyk1255HNxrGL97lnA2nfIz4q23XUU4AYjQkvWHVe94zbUGzdHM
> 6WZWLn8aZcugC5ltENAp7bCuye2KzpbA4BRbaoGBgiGRQaGSx+0poTubLODSNRFl
> cJv+KyoCS+NX4Lz0gK3sIhHr7xRQno5tYmUKNjIn3/v3Rt5zhjfXCvoElQ+MIlEW
> iQfkO6AMw+uWlNnd6Iuya9do4bYs/7oN4NiySy6yuz9v96JC6qjZvOtfj4nViNnm
> bTRNDreU8IyBR0/vkgKTNTF7KfebJ6ccxRUuFeqqK3rUikBVDW1SsKGskuQK+Htr
> I3y6BDq4qz2VjDdPTXL0
> =XGBI
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----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

Re: Upgrade to 8.5.8/9

Posted by Greg Huber <gr...@gmail.com>.
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.

Cheers Greg


On 19 December 2016 at 18:11, Christopher Schultz <
chris@christopherschultz.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> 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
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJYWCLGAAoJEBzwKT+lPKRYzqcP/R34lxIW90ZPn7SQ5SBsbKN8
> rvYD+4k7a3EGEnPUhfJaajOMbpTXdPTHyltHOID9CpRRFIGrb+/kcKmaLbllYIqq
> NUDvWSDUHK0yELaSjb7+Y980mygqXV3j8wAardcEnZ/wG143ZZozhpQtKjhpLmsb
> XMe0HiC9/4TeqCtyZ5IWRdq/UOotnU0m1QMjgGYQPztGwQlfvNYDZ//8apiYkCKY
> qUoblyNM1RiH4H6tiX+7ZEfk3exvArw84adcWULYiQNpHMwvsRlfMi1aq8Xcty5+
> xhB4SitKoEB6CY/oLwRjWYAUsQIov2trGoqbhxIiQcNpHxoKslLabvzdjmjMPMj0
> kbMiGpOFfK4ULqyk1255HNxrGL97lnA2nfIz4q23XUU4AYjQkvWHVe94zbUGzdHM
> 6WZWLn8aZcugC5ltENAp7bCuye2KzpbA4BRbaoGBgiGRQaGSx+0poTubLODSNRFl
> cJv+KyoCS+NX4Lz0gK3sIhHr7xRQno5tYmUKNjIn3/v3Rt5zhjfXCvoElQ+MIlEW
> iQfkO6AMw+uWlNnd6Iuya9do4bYs/7oN4NiySy6yuz9v96JC6qjZvOtfj4nViNnm
> bTRNDreU8IyBR0/vkgKTNTF7KfebJ6ccxRUuFeqqK3rUikBVDW1SsKGskuQK+Htr
> I3y6BDq4qz2VjDdPTXL0
> =XGBI
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Re: Upgrade to 8.5.8/9

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYWCLGAAoJEBzwKT+lPKRYzqcP/R34lxIW90ZPn7SQ5SBsbKN8
rvYD+4k7a3EGEnPUhfJaajOMbpTXdPTHyltHOID9CpRRFIGrb+/kcKmaLbllYIqq
NUDvWSDUHK0yELaSjb7+Y980mygqXV3j8wAardcEnZ/wG143ZZozhpQtKjhpLmsb
XMe0HiC9/4TeqCtyZ5IWRdq/UOotnU0m1QMjgGYQPztGwQlfvNYDZ//8apiYkCKY
qUoblyNM1RiH4H6tiX+7ZEfk3exvArw84adcWULYiQNpHMwvsRlfMi1aq8Xcty5+
xhB4SitKoEB6CY/oLwRjWYAUsQIov2trGoqbhxIiQcNpHxoKslLabvzdjmjMPMj0
kbMiGpOFfK4ULqyk1255HNxrGL97lnA2nfIz4q23XUU4AYjQkvWHVe94zbUGzdHM
6WZWLn8aZcugC5ltENAp7bCuye2KzpbA4BRbaoGBgiGRQaGSx+0poTubLODSNRFl
cJv+KyoCS+NX4Lz0gK3sIhHr7xRQno5tYmUKNjIn3/v3Rt5zhjfXCvoElQ+MIlEW
iQfkO6AMw+uWlNnd6Iuya9do4bYs/7oN4NiySy6yuz9v96JC6qjZvOtfj4nViNnm
bTRNDreU8IyBR0/vkgKTNTF7KfebJ6ccxRUuFeqqK3rUikBVDW1SsKGskuQK+Htr
I3y6BDq4qz2VjDdPTXL0
=XGBI
-----END PGP SIGNATURE-----

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