Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.io.UnsupportedEncodingException: Cp1386

12 views
Skip to first unread message

bob

unread,
Jul 24, 2002, 11:05:57 AM7/24/02
to
Does anyone know what might be causing this error, running WAS 4.0.2 AE on
Solaris 7

java.io.UnsupportedEncodingException: Cp1386
at sun.io.Converters.getConverterClass(Converters.java:107)
at sun.io.Converters.newConverter(Converters.java:138)
at
sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java:67)
at java.lang.String.getBTCConverter(String.java:124)
at java.lang.String.<init>(String.java:401)
at java.lang.String.<init>(String.java:422)
at
com.ibm.servlet.engine.webapp.RequestUtils.parseQueryString(RequestUtils.jav
a:256)
at
com.ibm.servlet.engine.srt.SRTServletRequest.parseParameters(SRTServletReque
st.java:617)
at
com.ibm.servlet.engine.srt.SRTServletRequest.getParameterNames(SRTServletReq
uest.java:342)
at
com.ibm.servlet.engine.webapp.HttpServletRequestProxy.getParameterNames(Http
ServletRequestProxy.java:191)
at com.lexus.util.JSPUtil.setRequestParameters(JSPUtil.java:838)
at com.lexus.control.web.Main.doGet(Main.java:167)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager
.java:827)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:167)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:297)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:110)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:47
2)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:1012)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:913)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:523)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:282)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:112)
at
com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:91)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:184)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:122)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:315)
at
com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.ja
va:60)
at
com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

Art Smet

unread,
Jul 24, 2002, 11:16:35 AM7/24/02
to
I'm guessing WebSphere is converting the "Accept-Language" value into a
particular encoding that is not supported on Solaris. Try examining
encoding.properties and converter.properties in your .../properties dir, Do you
see Cp1386 anywhere? Probably easiest for you to change that encoding to one
that is appropriate (and supported) on Solaris. You'll need to restart your app
server for the change to take effect.
0 new messages