KB-1094 "Unsupported encoding: XXXXX" error thrown when starting the application server

Parmida Borhani — Mon, 05 Nov 2018 22:20:15 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 11/5/2018 10:20:15 PM

Symptoms

When starting the application server, the following is printed towards the beginning of application server log:

Tomcat

WARNING [main] org.apache.catalina.startup.Catalina.load Catalina.start using conf/server.xml: 
java.io.UnsupportedEncodingException: UTF-XX

JBoss

Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

The application server then fails to deploy.

Cause

This "Caused by" message is printed out when one of the application server configuration files has been modified to an unsupported encoding mechanism. By default, encoding is set to UTF-8.

Tomcat

The opening line encoding ="UTF-8" of the server.xml file was changed. This file is located in <APPIAN_HOME>/tomcat/apace-tomcat/conf directory.

JBoss

The two following examples are results of using faulty configuration files:

standalone.xml

ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

appian-ds.xml

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."appian-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-mysql-ds.xml"
...
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unsupported encoding: XXXXX
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

In both examples above, the opening line encoding="UTF-8"? of the configuration files was changed. For reference, standalone.xml can be found under <JBOSS_HOME>/standalone/configuration and appian-ds.xml under <JBOSS_HOME>/standalone/deployments.

Action

Locate the problematic configuration file and change the encoding to UTF-8.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: application server, infrastructure

KB-1094 "Unsupported encoding: XXXXX" error thrown when starting the application server

Parmida Borhani — Mon, 05 Nov 2018 22:19:30 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 11/5/2018 10:19:30 PM

Symptoms

When starting the application server, the following is printed towards the beginning of application server log:

Tomcat

WARNING [main] org.apache.catalina.startup.Catalina.load Catalina.start using conf/server.xml:
java.io.UnsupportedEncodingException: UTF-XX

JBoss

Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

The application server then fails to deploy.

Cause

This "Caused by" message is printed out when one of the application server configuration files has been modified to an unsupported encoding mechanism. By default, encoding is set to UTF-8.

Tomcat

The opening line encoding ="UTF-8" of the server.xml file was changed. This file is located in <APPIAN_HOME>/tomcat/apace-tomcat/conf directory.

JBoss

The two following examples are results of using faulty configuration files:

standalone.xml

ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

appian-ds.xml

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."appian-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-mysql-ds.xml"
...
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unsupported encoding: XXXXX
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

Action

Locate the problematic configuration file and change the encoding to UTF-8.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: application server, infrastructure

KB-1094 "Unsupported encoding: XXXXX" error thrown when starting JBoss

Parmida Borhani — Mon, 30 Jul 2018 03:55:54 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 3:55:54 AM

Symptoms

When starting JBoss, the following error is printed towards the beginning of application server log:

Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

JBoss then fails to deploy.

Cause

This "Caused by" message is printed out when one of the Jboss configuration files has been modified to an unsupported encoding mechanism. By default, encoding is set to UTF-8.

The two following examples are results of using faulty configuration files:

standalone.xml

ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

appian-ds.xml

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."appian-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-mysql-ds.xml"
...
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unsupported encoding: XXXXX
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

Action

Locate the problematic configuration file and change the encoding to UTF-8.

Affected Versions

This article applies to all versions of Appian using JBoss as an application server.

Last Reviewed: February 2017

Tags: application server, infrastructure, jboss

KB-1094 "Unsupported encoding: XXXXX" error thrown when starting JBoss

Nick Vigilante — Wed, 22 Feb 2017 21:58:47 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/22/2017 9:58:47 PM

Symptoms

When starting JBoss, the following error is printed towards the beginning of application server log:

Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

JBoss then fails to deploy.

Cause

This "Caused by" message is printed out when one of the Jboss configuration files has been modified to an unsupported encoding mechanism. By default, encoding is set to UTF-8.

The two following examples are results of using faulty configuration files:

standalone.xml

ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

appian-ds.xml

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."appian-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-mysql-ds.xml"
...
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unsupported encoding: XXXXX
...
Caused by: com.ctc.wstx.exc.WstxIOException: Unsupported encoding: XXXXX

Action

Locate the problematic configuration file and change the encoding to UTF-8.

Affected Versions

This article applies to all versions of Appian using JBoss as an application server.

Last Reviewed: February 2017

Tags: application server, jboss