On 1/15/2014 10:13 AM, Тимур Кулибаев wrote: > Hello, Chris ! > > I applied settings you adviced: > ++++Don't you want user.langauge=RU user.country=kz? > > [oracle@n36 logs]$ echo $JAVA_OPTS > -XX:MaxPermSize=128M -Xms256m -Xmx1024m -Duser.language=RU -Duser.country=kz > > But our java-application gives the following message: > > 15.01.2014 21:41:01 org.apache.catalina.core.ApplicationContext log > MESSAGE = ORA-00604: error occurred at recursive SQL level 1 > ORA-12705: invalid or unknown NLS parameter value specified > , ERRORCODE = 604 > > ++++So, there can be problems in a couple of places. If you have an > ++++extended characters correctly-stored in the Oracle database, will it > ++++display correctly if you try to show it on a web page? Let's make sure > ++++that works first, then we'll tackle submitting such characters via > forms. > ++++Note that using extended characters in GET requests is a nightmare: > ++++you should try to avoid it at all costs. > > There are two state languages in Kazakhstan - Russian and Kazakh and both > must > be supported. Our Oracle database works in single-byte cyrillic encoding > and > its size is up to 1 tB now. If we convert one to Unicode it will be ~2 tB > which > is impossible for us as no disk space. > Our java servlet was created based on Oracle UIX technology which is old > enough. > Within seven years we successfully use this servlet with Oracle Application > Server 10g R2/R3 (now OAS 10.1.3.5). There are not any troubles with Kazakh > letters displaying on web-pages with Oracle Application Server. But Tomcat > gives > troubles with Kazakh letters displaying. What difference between Oracle > Application > Server and Tomcat in characters processing ? In production we still use > this > servlet with Oracle Application Server. I can see any its settings if you > tell me > which ones to check. > >From Tomcat doc I see that we can convert GET-request to specified code > page by > using "URIEncoding" in http-connector definition of server.xml. I have > tried to use > the followng: > <Connector port="7785" protocol="HTTP/1.1" > connectionTimeout="20000" > redirectPort="8443" > URIEncoding="Cp1251" <-- also tried Windows-1251, WINDOWS-1251, CP1251 > useBodyEncodingForURI="true"/> <--also tried without this one > > May be we must do some tracing to understand the root of the trouble ? > > Thank you for your helping me. > Waiting for your advices, > Timur
Hi, Timur- I've missed a good part of this thread but is the content type set either with the page directive or HttpServletResponse.setContentType()? -Terence Bandoian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
