Oracle database and cyrillic characters

[osjonathan]

I'm not sure if this is an issue with GeoNetwork or our Oracle, but the Cyrillic characters were causing my GeoNetwork to not function. Any page that would access a table like GROUPSDES would give back something like the following error:

HTTP ERROR: 500 The data "The data "@8<5@ 3@C??K" is not legal for a JDOM character content: 0x1f is not a legal XML character." is not legal for a JDOM character content: 0x1f is not a legal XML character.

RequestURI=/geonetwork/srv/en/group.list Caused by: org.jdom.IllegalDataException: The data "The data "@8<5@ 3@C??K" is not legal for a JDOM character content: 0x1f is not a legal XML character." is not legal for a JDOM character content: 0x1f is not a legal XML character.

at org.jdom.Text.setText(Text.java:188) at org.jdom.Text.(Text.java:99) at org.jdom.Element.setText(Element.java:630) at jeeves.exceptions.JeevesException.toElement(JeevesException.java:82) at jeeves.server.dispatchers.ServiceManager.getError(ServiceManager.java:825) at jeeves.server.dispatchers.ServiceManager.handleError(ServiceManager.java:454) at jeeves.server.dispatchers.ServiceManager.dispatch(ServiceManager.java:443) at jeeves.server.JeevesEngine.dispatch(JeevesEngine.java:670) at jeeves.server.sources.http.JeevesServlet.execute(JeevesServlet.java:185) at jeeves.server.sources.http.JeevesServlet.doGet(JeevesServlet.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)

Deleting all of the Russian language entries in the DES tables fixed it, but obviously something in the GeoNetwork/Oracle interaction was broken when it came to handling the Cyrillic characters. This was with a fresh 2.6.3 database.