KB-1736 HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Parmida Borhani — Thu, 04 Oct 2018 07:21:07 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 10/4/2018 7:21:07 AM

Symptoms

Appian and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

The JKWorkerProperty fields configured in Configuring Apache Web Server with Appian under Setup Worker Properties are specified in a file outside <APACHE_HOME>/conf/httpd.conf, rather than directly within it. Apache documentation indicates this is possible with the JkWorkersFile directive referencing a separate file called workers.properties, which contains the JKWorkerProperty fields.

However, the JkWorkersFile directive doesn't include the contents of workers.properties within httpd.conf. Trying to reference any worker names specified by the JKWorkerProperty field worker.list within httpd.conf will fail, causing the error in mod_jk.log.

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties.
2) Directly add the contents of workers.properties to httpd.conf.

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties in httpd.conf.

Affected Versions

This article applies to Appian 17.1 and later using Apache as a web server.

Last Reviewed: October 2018

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Wed, 03 Oct 2018 09:08:21 GMT

Revision 8 posted to Appian Knowledge Base by Zach Puderbach on 10/3/2018 9:08:21 AM

Symptoms

Appian and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

Action

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties in httpd.conf.

Affected Versions

This article applies to Appian 17.1 and later using Apache as a web server.

Last Reviewed: October 2018

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 13:53:18 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 1:53:18 PM

Symptoms

Tomcat and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:
[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

The 'JKWorkerProperty' fields from Setup Worker Properties are specified in a file outside <APACHE_HOME>/conf/httpd.conf, rather than directly within httpd.conf. Apache documentation indicates this is possible with the 'JkWorkersFile' directive to reference the 'JKWorkerProperty' fields as a separate file called workers.properties.

However, the 'JkWorkersFile' directive doesn't make the contents of the 'workers.properties' accessible within httpd.conf. Trying to reference any names specified by the 'JKWorkerProperty' field 'worker.list' within httpd.conf will fail, causing the error in mod_jk.log

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line JkWorkerFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties file.

Affected Versions

This article applies to Appian 17.1 and later

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 11:20:22 GMT

Revision 7 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 11:20:22 AM

Symptoms

Appian and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties in httpd.conf.

Affected Versions

This article applies to Appian 17.1 and later

Last Reviewed: October 2018

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 10:54:51 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 10:54:51 AM

Symptoms

Appian and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties in httpd.conf.

Affected Versions

This article applies to Appian 17.1 and later

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 10:54:07 GMT

Revision 5 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 10:54:07 AM

Symptoms

Tomcat and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties in httpd.conf.

Affected Versions

This article applies to Appian 17.1 and later

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 10:53:24 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 10:53:24 AM

Symptoms

Tomcat and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties in httpd.conf

Affected Versions

This article applies to Appian 17.1 and later

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 10:21:00 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 10:21:00 AM

Symptoms

Tomcat and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties.

Affected Versions

This article applies to Appian 17.1 and later

Tags: apache, web server, infrastructure

DRAFT KB-XXXX HTTP 500 Internal Server Error with "Could not find a worker for worker name" in mod_jk.log

Zach Puderbach — Tue, 02 Oct 2018 10:11:27 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 10/2/2018 10:11:27 AM

Symptoms

Tomcat and Apache start successfully, but a HTTP 500 Internal Server Error appears when trying to access the Appian login page.

The <APACHE_HOME>/logs/mod_jk.log file shows the following error:

[info] init_jk::mod_jk.c (3595): mod_jk/1.2.42 initialized
[info] jk_handler::mod_jk.c (3003): Could not find a worker for worker name=LoadBalancer”

Cause

The JKWorkerProperty fields configured in Setup Worker Properties are specified in a file outside <APACHE_HOME>/conf/httpd.conf, rather than directly within it. Apache documentation indicates this is possible with the JkWorkersFile directive referencing a separate file called workers.properties, which contains the JKWorkerProperty fields.

Action

Follow the Appian Documentation Configuring Apache Web Server with Appian under Setup Worker Properties (or Configuring Apache Web Server with Jboss in 18.2 and below) when configuring the JKWorkerProperty fields.
1) Remove the line using the JkWorkersFile directive: JkWorkersFile /path/to/workers.properties
2) Directly add the contents of workers.properties to httpd.conf

Workaround

Instead of following the action steps, add the line Include conf/workers.properties after the line JkWorkerFile /path/to/workers.properties.

Affected Versions

This article applies to Appian 17.1 and later

Tags: apache, web server, infrastructure