Fatal error: The encoding "Cp1252" is not supported.

Gary Ivey

Additional info from the log

2002-02-01 15:18:12 UserDatabaseRealm[Standalone]: Exception looking up UserDatabase under key catalina/UserDatabase
javax.naming.NamingException: Stopping after fatal error: The encoding "Cp1252" is not supported.
	at org.apache.naming.NamingContext.lookup(Unknown Source)
	at org.apache.naming.NamingContext.lookup(Unknown Source)
	at org.apache.naming.NamingContext.lookup(Unknown Source)
	at org.apache.naming.NamingContext.lookup(Unknown Source)
	at org.apache.catalina.realm.UserDatabaseRealm.start(Unknown Source)
	at org.apache.catalina.core.ContainerBase.start(Unknown Source)
	at org.apache.catalina.core.StandardEngine.start(Unknown Source)
	at org.apache.catalina.core.StandardService.start(Unknown Source)
	at org.apache.catalina.core.StandardServer.start(Unknown Source)
	at org.apache.catalina.startup.Catalina.start(Unknown Source)
	at org.apache.catalina.startup.Catalina.execute(Unknown Source)
	at org.apache.catalina.startup.Catalina.process(Unknown Source)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.apache.catalina.startup.Bootstrap.main(Unknown Source)


There is a reported bug (nr. 5488) regarding this problem. Actually, the file tomcat-users.xml gets changed to:

<?xml version='1.0' encoding='Cp1252'?>
<tomcat-users>
<user username='both' password='tomcat' roles='tomcat,role1'/>
<user username='role1' password='tomcat' roles='role1'/>
<user username='tomcat' password='tomcat' roles='tomcat'/>
</tomcat-users>

If I change the ‘Cp1252’ to ‘ISO-8859-1’ Tomcat will run again. It gets changed back when I run the startup.bat. The workaround in the bug report states:

The workaround is to remove the encoding attribute from the XML after Tomcat expands the WAR file.
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

About | Sitemap | Contact