I have set up a very simple Apache + Glassfish cluster configuration.

It works fine if I create and use a listener that use the default http-listener-1.

However, if I switch to a secure listener which use http-listener-2 then the connection is established but then it is dropped with the user getting the 502 Bad Gateway error, and I have this message in mod_jk.log

[Wed Dec 04 16:17:55.905 2019] [6957:139970911750336] [debug] jk_open_socket::jk_connect.c (674): socket TCP_NODELAY set to On
[Wed Dec 04 16:17:55.905 2019] [6957:139970911750336] [debug] jk_open_socket::jk_connect.c (711): socket SO_KEEPALIVE set to On
[Wed Dec 04 16:17:55.905 2019] [6957:139970911750336] [debug] jk_open_socket::jk_connect.c (763): timeout 300 set for socket=16
[Wed Dec 04 16:17:55.905 2019] [6957:139970911750336] [debug] jk_open_socket::jk_connect.c (798): trying to connect socket 16 to
[Wed Dec 04 16:17:55.906 2019] [6957:139970911750336] [debug] jk_open_socket::jk_connect.c (824): socket 16 [ ->] connected

other log entries in between....

[Wed Dec 04 16:17:55.907 2019] [6957:139970911750336] [debug] ajp_send_request::jk_ajp_common.c (1779): (worker1) request body to send 0 - request body to resend 0
[Wed Dec 04 16:17:55.909 2019] [6957:139970911750336] [debug] jk_shutdown_socket::jk_connect.c (931): About to shutdown socket 16 [ ->]
[Wed Dec 04 16:17:55.909 2019] [6957:139970911750336] [debug] jk_is_input_event::jk_connect.c (1410): error event during poll on socket 16 [ ->] (event=16)
[Wed Dec 04 16:17:55.909 2019] [6957:139970911750336] [debug] jk_shutdown_socket::jk_connect.c (1015): Shutdown socket 16 [ ->] and read 0 lingering bytes in 0 sec.
[Wed Dec 04 16:17:55.909 2019] [6957:139970911750336] [info] ajp_connection_tcp_get_message::jk_ajp_common.c (1339): (worker1) can't receive the response header message from tomcat, tomcat ( has forced a connection close for socket 16

The configuration is quite standard, the only difference is that I am using a personal certificate built with my internal certification authority. The certificate have been successfully added to the keystore and if I access the web app directly trough port 8181 it works (with some warning) and I can inspect my certificate.

Here is the https.conf part

  # Sample app
  JkMount /sample loadbalancer
  JkMount /sample/* loadbalancer

the workers.properties


# default properties for workers

# properties for worker1

# properties for loadbalancer

Here the jk connector on Glassfish, as you see it's on port 28010, which I have made sure it is open.

enter image description here

1 Answer 1


After having spent some time in investigating this issue and reading documents, I came to the conclusion that JK is not working with TLS. The security flag only applies to http listener.

One possible working options I have experimented is to open a tunnel between the HTTPD and the Glassfish instances. It's easy, but it may have some downside. The most important is that the SSH connection may goes down. Building a service that restart the tunnel in this case can be also done, but it was beyond my knowledge (and timing).

Because the network on which the instances reside is already well protected, I ended up with communicating to JK trough a non secure connection.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.