KB-1745 Users are unable to login to Appian with exception "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Jordan Horwat — Thu, 11 Oct 2018 09:30:29 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 10/11/2018 9:30:29 AM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to the Post-Install Configurations documentation, so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Tom Ryan — Tue, 09 Oct 2018 00:32:13 GMT

Revision 14 posted to Appian Knowledge Base by Tom Ryan on 10/9/2018 12:32:13 AM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to the Post-Install Configurations documentation, so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Thu, 04 Oct 2018 11:55:17 GMT

Revision 13 posted to Appian Knowledge Base by Daniel DeVeau on 10/4/2018 11:55:17 AM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to the Post-Install Configurations documentation, so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Jordan Horwat — Wed, 03 Oct 2018 16:30:26 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 10/3/2018 4:30:26 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to the Post-Install Configurations documentation, so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Jordan Horwat — Wed, 03 Oct 2018 16:30:11 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 10/3/2018 4:30:11 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following error in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to the Post-Install Configurations documentation, so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Jordan Horwat — Wed, 03 Oct 2018 16:27:55 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 10/3/2018 4:27:55 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to the Post-Install Configurations documentation, so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: October 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Jordan Horwat — Wed, 03 Oct 2018 16:24:54 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 10/3/2018 4:24:54 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The conf.suite.SCHEME property is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian with exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Tue, 02 Oct 2018 15:21:06 GMT

Revision 8 posted to Appian Knowledge Base by Daniel DeVeau on 10/2/2018 3:21:06 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The "conf.suite.SCHEME" is incorrectly configured in <APPIAN_HOME>/conf/custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME is uncommented and set to the correct value.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Thu, 27 Sep 2018 14:38:14 GMT

Revision 7 posted to Appian Knowledge Base by Daniel DeVeau on 9/27/2018 2:38:14 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: September 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Wed, 26 Sep 2018 17:20:15 GMT

Revision 6 posted to Appian Knowledge Base by Daniel DeVeau on 9/26/2018 5:20:15 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: January 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Tejas Kargutkar — Wed, 26 Sep 2018 14:50:32 GMT

Revision 5 posted to Appian Knowledge Base by Tejas Kargutkar on 9/26/2018 2:50:32 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: January 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Users are unable to login to Appian exception, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Wed, 26 Sep 2018 09:42:46 GMT

Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 9/26/2018 9:42:46 AM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: January 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Unable to login to Appian with error in Tomcat logs, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Wed, 26 Sep 2018 09:40:21 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 9/26/2018 9:40:21 AM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: January 2018

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Unable to login to Appian with error in Tomcat logs, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Tue, 25 Sep 2018 20:29:15 GMT

Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 9/25/2018 8:29:15 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, application server, infrastructure

DRAFT KB-XXXX Unable to login to Appian with error in Tomcat logs, "java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens"

Daniel DeVeau — Tue, 25 Sep 2018 16:29:42 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 9/25/2018 4:29:42 PM

Symptoms

All users are unable to login to Appian with the message:

'Error401 - Unauthorized: Sorry, your request could not be processed'

Tomcat logs the following in <APPIAN_HOME>/logs/tomcat-stdOut.log:

Error parsing HTTP request header
java.lang.IllegalArgumentException: Invalid character found in method name. HTTP method names must be tokens

Cause

The scheme is incorrectly configured in custom.properties.

Action

Ensure custom.properties is configured according to installation documentation so that the line conf.suite.SCHEME=http is uncommented.
Restart Tomcat.

Affected Versions

This article applies to Appian 18.3 and later.

Tags: Tomcat, application server, infrastructure