cp1252 encoding exception during Tomcat6 server startup on Windows [message #1006580] |
Thu, 31 January 2013 21:56 |
|
Hi,
I've deployed a Stardust 0.7 Spring WAR on Tomcat 6 and the application seems to startup fine (according to the log), but then it shuts itself down immediately. There's nothing in the stardust log, but I'm getting the following stacktrace in the catalina.log of the server.
INFO: Starting Servlet Engine: Apache Tomcat/6.0.36
Jan 31, 2013 4:49:35 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor ipp-portal.xml
Jan 31, 2013 4:49:36 PM org.apache.catalina.core.StandardContext addApplicationListener
INFO: The listener "com.icesoft.faces.util.event.servlet.ContextEventRepeater" is already configured for this context. The duplicate definition has been ignored.
Jan 31, 2013 4:49:36 PM org.apache.catalina.core.StandardContext addApplicationListener
INFO: The listener "org.apache.myfaces.webapp.StartupServletContextListener" is already configured for this context. The duplicate definition has been ignored.
Jan 31, 2013 4:49:57 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Jan 31, 2013 4:50:04 PM com.sun.xml.wss.jaxws.impl.SecurityServerTube configureServerHandler
SEVERE: WSSTUBE0027: Error in configuring Server Security Callback Handler.
java.lang.RuntimeException: org.xml.sax.SAXParseException: Invalid encoding name "cp1252".
at com.sun.xml.wss.impl.misc.DefaultRealmAuthenticationAdapter.populateTomcatUsersXML(DefaultRealmAuthenticationAdapter.java:275)
at com.sun.xml.wss.impl.misc.DefaultRealmAuthenticationAdapter.<init>(DefaultRealmAuthenticationAdapter.java:96)
at com.sun.xml.wss.RealmAuthenticationAdapter.newInstance(RealmAuthenticationAdapter.java:147)
at com.sun.xml.wss.jaxws.impl.SecurityServerTube.getRealmAuthenticationAdapter(SecurityServerTube.java:767)
at com.sun.xml.wss.jaxws.impl.SecurityServerTube.configureServerHandler(SecurityServerTube.java:733)
at com.sun.xml.wss.jaxws.impl.SecurityServerTube.<init>(SecurityServerTube.java:150)
at com.sun.xml.wss.provider.wsit.SecurityTubeAppender.appendTube(SecurityTubeAppender.java:129)
at com.sun.xml.ws.assembler.TubelineAssemblerFactoryImpl$WsitTubelineAssembler.createServer(TubelineAssemblerFactoryImpl.java:101)
at com.sun.xml.ws.server.WSEndpointImpl.<init>(WSEndpointImpl.java:152)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:218)
at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters(DeploymentDescriptorParser.java:253)
at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse(DeploymentDescriptorParser.java:147)
at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:108)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
at org.apache.catalina.core.StandardService.start(StandardService.java:525)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Caused by: org.xml.sax.SAXParseException: Invalid encoding name "cp1252".
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.sun.xml.wss.impl.misc.DefaultRealmAuthenticationAdapter.populateTomcatUsersXML(DefaultRealmAuthenticationAdapter.java:254)
... 37 more
|
|
|
Re: cp1252 encoding exception during Tomcat6 server startup on Windows [message #1007179 is a reply to message #1006580] |
Mon, 04 February 2013 19:01 |
|
The problem in this case came from one of the files installed by Tomcat itself. The "tomcat-users.xml" file was the only one which had a "cp1252" encoding in the XML prolog.
Changing it to "UTF-8" solved the problem. (Usually you'd make sure the file is really UTF-8 encoded by opening it in an appropriate text editor, but here the file is not really used anyways ...).
Jan
|
|
|
Powered by
FUDForum. Page generated in 0.03271 seconds