SAX FATAL:Unconvertible UTF-8 character

Is there someone that knows how to eliminate this annoying error, that randomly
appears(it seems to appear every time I reboot the system...)?
Whe have seen this problem running wlps 3.2 on several machines, linux, solaris
and winnt, all pointing to some oracle database 8.1.6 with thin jdbc driver
Reloading the WLCS_RULESET_DEFINITION table from another stable environment eliminate
the problem...
Fri Nov 02 11:04:29 CET 2001:<I> <JDBC Pool> Connection for pool "commercePool"
created.
SAX FATAL[ejb://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/RegoleLogoBanca:1,-1]:
Character conversion error: "Unconvertible UTF-8 character beginning with 0xbb"
(line number may be too low).
Fri Nov 02 11:04:30 CET 2001:<E> <T3Services> COMMERCE_SERVER_FRAMEWORK,LOG_ERROR,"Error
in AdvisorBean.advise() : Exception com.beasys.commerce.axiom.reasoning.rules.service.RulesServiceException
thrown while processing advislet : com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdviceRequestImpl)."
com.beasys.commerce.axiom.advisor.AdvisorException: Rules Service RulesServiceException
thrown : RulesService:Unable to apply rules :: RulesService:Unable to get context
wrapper :: RulesService:Unable to create context wrapper :: RulesService:Unable
to create ruleset for xml rules :: org.xml.sax.SAXParseException: Character conversion
error: "Unconvertible UTF-8 character beginning with 0xbb" (line number may be
too low).
at com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(ContentSelectorAdvisletImpl.java:157)
at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:100)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ContentSelectorTag:Unable to get advice:
com.beasys.commerce.axiom.advisor.AdvisorException: Exception thrown during Advislet.advise
method
at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:117)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ContentSelectorTag:Unable to evaluate tag:
javax.servlet.jsp.JspTagException: ContentSelectorTag:Unable to get advice.
at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:160)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)

Fulvio - for an answer to this, refer to my post in the other thread that you started.
PJL
"fulvio" <[email protected]> wrote:
>
Is there someone that knows how to eliminate this annoying error, that
randomly
appears(it seems to appear every time I reboot the system...)?
Whe have seen this problem running wlps 3.2 on several machines, linux,
solaris
and winnt, all pointing to some oracle database 8.1.6 with thin jdbc
driver
Reloading the WLCS_RULESET_DEFINITION table from another stable environment
eliminate
the problem...
Fri Nov 02 11:04:29 CET 2001:<I> <JDBC Pool> Connection for pool "commercePool"
created.
SAX FATAL[ejb://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/RegoleLogoBanca:1,-1]:
Character conversion error: "Unconvertible UTF-8 character beginning
with 0xbb"
(line number may be too low).
Fri Nov 02 11:04:30 CET 2001:<E> <T3Services> COMMERCE_SERVER_FRAMEWORK,LOG_ERROR,"Error
in AdvisorBean.advise() : Exception com.beasys.commerce.axiom.reasoning.rules.service.RulesServiceException
thrown while processing advislet : com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdviceRequestImpl)."
com.beasys.commerce.axiom.advisor.AdvisorException: Rules Service RulesServiceException
thrown : RulesService:Unable to apply rules :: RulesService:Unable to
get context
wrapper :: RulesService:Unable to create context wrapper :: RulesService:Unable
to create ruleset for xml rules :: org.xml.sax.SAXParseException: Character
conversion
error: "Unconvertible UTF-8 character beginning with 0xbb" (line number
may be
too low).
at com.beasys.commerce.axiom.advisor.advislets.ContentSelectorAdvisletImpl.advise(ContentSelectorAdvisletImpl.java:157)
at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:100)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ContentSelectorTag:Unable to get advice:
com.beasys.commerce.axiom.advisor.AdvisorException: Exception thrown
during Advislet.advise
method
at com.beasys.commerce.axiom.advisor.AdvisorBean.advise(AdvisorBean.java:117)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl.advise(AdvisorBeanEOImpl.java:103)
at com.beasys.commerce.axiom.advisor.AdvisorBeanEOImpl_ServiceStub.advise(AdvisorBeanEOImpl_ServiceStub.java:190)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:151)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)
at bsella.jsp._Autenticazione._servletpage._AuthenticationLevelTwoParams._jspService(_AuthenticationLevelTwoParams.java:203)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:124)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at it.sella.authentication.servlet.SellaAuthenticationServlet.includePageInResponse(SellaAuthenticationServlet.java:1716)
at it.sella.authentication.servlet.SellaAuthenticationServlet.displayAuthenticationPages(SellaAuthenticationServlet.java:1620)
at it.sella.authentication.servlet.SellaAuthenticationServlet.processLogin(SellaAuthenticationServlet.java:1047)
at it.sella.authentication.servlet.SellaAuthenticationServlet.service(SellaAuthenticationServlet.java:539)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
ContentSelectorTag:Unable to evaluate tag:
javax.servlet.jsp.JspTagException: ContentSelectorTag:Unable to get advice.
at com.beasys.commerce.p13n.tags.ContentSelectorTag.getDocuments(ContentSelectorTag.java:160)
at com.beasys.commerce.p13n.tags.ContentSelectorTag.doStartTag(ContentSelectorTag.java:112)

Similar Messages

Character conversion error: Unconvertible UTF-8 character beginning..

Hello,
I'm using TrAX for XSLT transformations, and having a following
problem
Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
        at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
        at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
        at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
        at org.apache.crimson.parser.Parser2.maybeTextDecl(Parser2.java:2795)
        at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.java:2880)
        at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1167)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
        at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
        at mlts.converter.XMLImport.outputESGML(XMLImport.java:311)
        at mlts.converter.Converter.processFile(Converter.java:312)
        at mlts.converter.Converter.Convert(Converter.java:229)
        at test.main(test.java:7)Following the source code, I've found that the exception is thrown
when it reads DTD. I tried to read DTD using InputSource
in ascii, in latin-1 and my program reads it without any problem.
I really appreciate any help,
Thanks

http://forum.java.sun.com/thread.jsp?forum=34&thread=254927

Error during JLOAD import with Unconvertible UTF-8 character

Dear gurus,
I'm performing a system copy on ECC 6.0. SR£ double stack. During the face of jload import I receive the error
Unconvertible UTF-8 character beginning with 0xf9
while importing the table TST_RESERVATION.
Here you are the full text of the error
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_31-b03, mixed mode)
org.xml.sax.SAXException: Fatal Error: URI=null Line=1: Errore di conversione caratteri: "Unconvertible UTF-8 character beginning with 0xf9" (il numero riga potrebbe essere troppo basso).
     at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)
     at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1106)
     at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
     at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
     at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
     at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)
     at com.sap.dictionary.database.dbs.DbObjectModificationAnalyser.(DbObjectModificationAnalyser.java:38)
     at com.sap.dictionary.database.opentools.DbTableOpenTools.createTable(DbTableOpenTools.java:70)
     at com.sap.inst.jload.db.DBTable.create(DBTable.java:106)
     at com.sap.inst.jload.Jload.dbImport(Jload.java:278)
     at com.sap.inst.jload.Jload.executeJob(Jload.java:397)
     at com.sap.inst.jload.Jload.main(Jload.java:621)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:331)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
any sugggestion?
plese advise soon.

Hi,
Are the files from the Java-CD fully readable and fully copied, for instance the java-dumpfile ?
Ensure JVM settings of note # 716604 area applied. Also, is connect possible to database by 'configtool' or does it throw an error ?
Br,
Javier

Character conversion error: "Unconvertible UTF-8 character beginning with 0

Hi All,
I developed an Adapter Module and added to Adapter Framework.
package sample;
import java.io.InputStream;
import java.text.SimpleDateFormat;
import java.util.Date;
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
import com.sap.aii.af.mp.module.Module;
import com.sap.aii.af.mp.module.ModuleContext;
import com.sap.aii.af.mp.module.ModuleData;
import com.sap.aii.af.mp.module.ModuleException;
import com.sap.aii.af.ra.ms.api.Message;
import com.sap.aii.af.ra.ms.api.XMLPayload;
@ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
@ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
@ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
@ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
@stateless
public class SetAttachmentName implements SessionBean, Module {
     private SessionContext myContext;
     private String mailFileName = "UStN";
     public void ejbRemove() {
     public void ejbActivate() {
     public void ejbPassivate() {
     public void setSessionContext(SessionContext context) {
          myContext = context;
     public void ejbCreate() throws CreateException {
     public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          // create a second attachment for the receiver mail adapter
          try {
               //                  get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               //               creating parsable XML document
               InputStream XIStreamData = null;
               XMLPayload xmlpayload = msg.getDocument();
               XIStreamData = xmlpayload.getInputStream();
               DocumentBuilderFactory docBuilderFactory =
                    DocumentBuilderFactory.newInstance();
               DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
               Document doc = docBuilder.parse(XIStreamData);
               //            finding the tag's name from the Modules tab in the Directory that will hold the attachment's name
               String absenderIDTag = null;
               absenderIDTag = moduleContext.getContextData("<RCVPRN>");
               //            finding the content of the tag that will be used as the attachment's name (assuming it's the only tag with this name)
               Element element = doc.getDocumentElement();
               NodeList list = doc.getElementsByTagName(absenderIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().toString();
               String anIDTag = null;
               anIDTag = moduleContext.getContextData("<CREDAT>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(anIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().toString();
               Date date = new Date(System.currentTimeMillis());
               //            Add date to the Message
               SimpleDateFormat dateFormat = new SimpleDateFormat("yyyyMMdd");
               mailFileName += "_" + dateFormat.format(date);
               String belegNummerTag = null;
               belegNummerTag = moduleContext.getContextData("<BULK_REF>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(belegNummerTag);
               mailFileName += "_" + list.item(0).getFirstChild().toString();
               //               creating the attachment
               byte by[] = xmlpayload.getText().getBytes();
               XMLPayload attachmentPDF = msg.createXMLPayload();
               attachmentPDF.setName(mailFileName);
               attachmentPDF.setContentType("application/pdf");
               attachmentPDF.setContent(by);
               //adding the message to the attachment
               msg.addAttachment(attachmentPDF);
               //                  provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               //                  raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
          //                  return XI message
          return inputModuleData;
I get the following error
Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
Any tips, pointers ?
Thanks in Advance
Mukhtar

Hi Henrique,
I am using .getNodeValue()
import java.io.InputStream;
import java.text.SimpleDateFormat;
import java.util.Date;
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
import com.sap.aii.af.mp.module.*;
import com.sap.aii.af.ra.ms.api.*;
@ejbHome <{com.sap.aii.af.mp.module.ModuleHome}>
@ejbLocal <{com.sap.aii.af.mp.module.ModuleLocal}>
@ejbLocalHome <{com.sap.aii.af.mp.module.ModuleLocalHome}>
@ejbRemote <{com.sap.aii.af.mp.module.ModuleRemote}>
@stateless
public class UStNAttachmentName3 implements SessionBean, Module {
     private SessionContext myContext;
     private String mailFileName = "UStN";
     public void ejbRemove() {
     public void ejbActivate() {
     public void ejbPassivate() {
     public void setSessionContext(SessionContext context) {
          myContext = context;
     public void ejbCreate() throws CreateException {
     public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          // create a second attachment for the receiver mail adapter
          try {
               // get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               // creating parsable XML document
               InputStream XIStreamData = null;
               XMLPayload xmlpayload = msg.getDocument();
               XIStreamData = xmlpayload.getInputStream();
               DocumentBuilderFactory docBuilderFactory =
                    DocumentBuilderFactory.newInstance();
               DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
               Document doc = docBuilder.parse(XIStreamData);
               // finding the tag's name from the Modules tab in the Directory that will hold the attachment's name
               String absenderIDTag = null;
               absenderIDTag = moduleContext.getContextData("<RCVPRN>");
               // finding the content of the tag that will be used as the attachment's name (assuming it's the only tag with this name)
               Element element = doc.getDocumentElement();
               NodeList list = doc.getElementsByTagName(absenderIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
               String anIDTag = null;
               anIDTag = moduleContext.getContextData("<CREDAT>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(anIDTag);
               mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
               Date date = new Date(System.currentTimeMillis());
               // Add date to the Message
               SimpleDateFormat dateFormat = new SimpleDateFormat("yyyyMMdd");
               mailFileName += "_" + dateFormat.format(date);
               String belegNummerTag = null;
               belegNummerTag = moduleContext.getContextData("<BULK_REF>");
               element = doc.getDocumentElement();
               list = doc.getElementsByTagName(belegNummerTag);
               mailFileName += "_" + list.item(0).getFirstChild().getNodeValue();
               // creating the attachment
               byte by[] = xmlpayload.getText().getBytes();
               XMLPayload attachmentPDF = msg.createXMLPayload();
               attachmentPDF.setName(mailFileName);
               attachmentPDF.setContentType("application/pdf");
               attachmentPDF.setContent(by);
               //adding the message to the attachment
               msg.addAttachment(attachmentPDF);
               // provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               // raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
          // return XI message
          return inputModuleData;
Still I get the same error.
org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
Adapter-Framework: Character conversion error: "Unconvertible UTF-8 character beginning with 0xaa" (line number may be too low).
Regards,
Mukhtar

Unconvertible UTF-8 Character error

Hi All ,
I have a problem while parsing a XML which has some Special characters
like, '�', '�', '�' etc.
The error is as follows :
org.xml.sax.SAXParseException : Character conversion error : "Unconvertible
UTF-* character begining with 0x96" (line number may be too low)
Could you please help me out here ....
thanx
Bibhu

This problem is related to the xml encoding. When using non-ascii characters you should specify which encoding is used in the document.
For instance,
<?xml version="1.0" encoding="ISO-8859-9"?>
The encoding code depends on the locale of your text editor or operating system. You can check it by the system property file.encoding.
From the following page you can obtain more information about xml encoding: http://www.w3schools.com/xml/xml_encoding.asp
Best regards...
Mert Nuhoglu

Org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x80) was found in the CDATA section

          Hi,
          I,'m using c.tld tag libraries from Yakarta in order to use c:if functions.
          When I use non-unicode characters in my JSP pages, it crashes:
          java.io.IOException: javax.servlet.jsp.JspException: The taglib validator rejected
          the page: "org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x80)
          was found in the CDATA section., "
               at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:124)
               at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
               at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:353)
               at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:211)
               at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:149)
               at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:521)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:351)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5445)
               at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          How can I force it to use ISO-8859-1? All my tries haven't work. What should I
          do? The c.tld libraries and jars are taken from JDK 1.4.1_02


Hi Stefan,
   This is my source xml in moni..
xmlns:prx="urn:sap.com:proxy:ECP:/1SAI/TAS5BFDF495190544E4B506:701:2008/06/06">
<SiteId>0080</SiteId>
<UCC>42027519 91029010015</UCC>
My interface is SAP(Proxy) to Database(Synchronous).
   SAP (PROXY) --> PI --> DATABASE ( Synchronous Communication )
Let me know if u need any information from my side...
Thanks for ur help...
Thanks,
Siva..

Invalid Characters shown in UTF-8 character set

There is an XMLP report whose template output character set is ISO-8859-1. The character set ISO-8859-1 is required for this report as per Spanish Authorities. When the report is run, output gets generated in the output directory file of application server. This output file doesn't contain any invalid characters.
But when the output is opened from SRS window, which opens it in a browser, the invalid characters are shown for characters like Ñ , É etc.
Investigation done:
Found that the output generated on the server is having ISO encoding and hence doesn't contain any invalid characters. Whereas the output generated from SRS window, it is in UTF encoding, so it seems the invalid characters are displayed when conversion takes place from ISO to UTF-8 format.
Created the eText output using the data xml and template using BI publisher tool, the output is in ISO encoding. So if i go and change the encoding to UTF-8 by opening it in explorer or Notepad++, invalid charcters are shown for Ñ, É etc.
Is there any limitation, that output from SRS window will show only in UTF-8 encoding? If not then please suggest.
Thanks,
Saket
Edited by: 868054 on Aug 2, 2012 3:05 AM
Edited by: 868054 on Aug 2, 2012 3:05 AM

Hi Srini,
When customer is viewing output from the SRS window, then it contains invalid characters because it is in UTF-8 character set. Customer is on Oracle OnDemand so they cannot take the output generated on the server.Every time they have to raise a request to Oracle for the output file. So the concern here is, why don't the output from SRS window show output with valid characters ?
The reason could be conversion of ISO format to UTF-8. How could this be resolved ? Does SRS window output cannot generate in ISO format ?
A quick reply will be appreciated as customer is chasing for an update.
Thanks,
Saket
Edited by: 868054 on Aug 7, 2012 11:08 PM

UTF-8 character in transforamtion

Hi,
I need to send the character from XML file to database adapter in UTF-8 character, is there any function available to do it in transformation.
Actual problem:
Source legacy system is in ISO-8859-1 and it is generating the XML file and converting text in it to UTF-8 character. So £ sign in XML file when reaches to Target system in UTF-8 it becaomes Â£.
But when BPEL insert it to database it is not inserting as £ but inserting it as Â£. My database character set is also UTF-8.
Any idea please suggest.
Regards,
Sreejit

Make sure that your database is running in UTF characters set. If not, you coudl use a PL/SQL function to converts from charset to charset:
http://orasoa.blogspot.com/2007/02/characterset-conversion.html
Marc

Non UTF-8 Character in V$session

Hello
The oracle clusterware process racgimon is putting a Non utf-8 character into v$session and so causing problems. The value is NT-AUTORITÄT\SYSTEM. Any ideas of how to correct this ?
Database Parameters
NLS_LANGUAGE     GERMAN
NLS_TERRITORY     GERMANY
NLS_CHARACTERSET     AL32UTF8
Thank you.

I did something along that line (but I used a different test account since System account localisation is different on my test machine) - see below.
So far it would seem the case is that certain characters (code) in v$session.osuser is not handled properly, in general, not only for racgimon.exe.
Perhaps the assumption is that os account names for 'osuser' consists of ascii characters only (and read as such, even if codes 0x80-FF is used).
The value of CharacterSet from dump() output above is misleading for this column as it isn't 'typed' correctly (as you say, non utf-8 representation), as it would be with regular tables'. Still, I believe something similar to "pass-through scenario" is going on.
Note on the use of [url http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/functions027.htm]convert function, as it should not be used, however it says "+...the only practical use of the function is to correct data that has been stored in a wrong character set.+" which would seem to apply here, so I guess this temporary use of convert is ok.
The account setup for test is AüTÄT, just to involve some non-ascii characters.
SQL> select osuser
, dump(osuser,16) dump_incorrect_chars
, convert(osuser,'al32utf8','we8mswin1252') osusercorr
, dump(convert(osuser,'al32utf8','we8mswin1252'),16) dump_corrected
from v$session
where program = 'sqlplus.EXE';
OSUSER               DUMP_INCORRECT_CHARS
OSUSERCORR           DUMP_CORRECTED
Odd7\A¿T¿            Typ=1 Len=10: 4f,64,64,37,5c,41,fc,54,c4,54
Odd7\AüTÄT           Typ=1 Len=12: 4f,64,64,37,5c,41,c3,bc,54,c3,84,54I also found that oracle.exe process itself, started under Localsystem, is using a "common" name instead. It shows up as SYSTEM instead of LocalSystem or principal name in v$session.osuser. Perhaps this is related to how/from where process is spawned, via SCM or not (e.g. Scheduler).
SQL> select sid, osuser, program from v$session;
SID OSUSER               PROGRAM
   2 SYSTEM               ORACLE.EXE (PMON)
15 SYSTEM               ORACLE.EXE (MMON)
16 SYSTEM               ORACLE.EXE (MMNL)
17 NT instans\SYSTEM    sqlplus.EXEI guess, to avoid this mess, we need to find some workaround such as:
- change the client process os account i.e. start as .\Localsystem or account other than Localsystem.
- change locale for the user account so that non localised name NT-AUTHORITY\SYSTEM is used
- change the way process is started, so that user name is picked up without the NT-AUTORITÄT prefix.
Hope this helps.
Edited by: orafad on May 25, 2011 1:59 PM
Edited by: orafad on May 25, 2011 2:25 PM

Using Direct Input mode: UTF-8 character encoding assumed

When I validate a web page in dreamweaver CS5 (using Jeffrey Zeldman's Web Standards Advisor ) I receive the following warning; Using Direct Input mode: UTF-8 character encoding assumed.
However if I validate using W3C either as a file upload or via the live site the page validates correctly.
Can anybody please help, as it is driving me insane.

Hi John
Thank you for your swift response,
As I said before this only happens locally within Dreamweaver CS5.
However The web address is www.countryimage.co.uk/index.htm
As you will see from the code I have included <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> within the head

Or.xml.sax giving error when parsing character entity

I am parsing an xml stream using SAX parser using org.xml.sax.*
When any XML tag say <name>sumit & sumit</name> OR <name>sumit & sumit</name> is parsed it throws the error as :
org.xml.sax.SAXParseException: XML-0210: (Fatal Error) Unexpected EOF.
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at org.xml.sax.SAXException.<init>(Compiled Code)
at org.xml.sax.SAXParseException.<init>(Compiled Code)
at oracle.xml.parser.v2.XMLParseException.<init>(Compiled Code)
at oracle.xml.parser.v2.XMLError.flushErrors(Compiled Code)
at oracle.xml.parser.v2.XMLError.error(Compiled Code)
at oracle.xml.parser.v2.XMLError.error(Compiled Code)
at oracle.xml.parser.v2.XMLReader.popXMLReader(Compiled Code)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(Compiled Code)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(Compiled Co
de)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(Compiled Code)
at oracle.xml.parser.v2.XMLParser.parse(Compiled Code)
at com.fidelity.fbrs.general.process.GenericSAXHandler.parse(Compiled Co
de)
at com.fidelity.fbrs.general.process.ServiceRequest.processComplexXMLReq
uest(Compiled Code)
at com.fidelity.fbrs.general.process.ServiceRequest.processXMLRequest(Co
mpiled Code)
at com.fidelity.fbrs.general.process.ServiceRequest.service(Compiled Cod
e)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at org.apache.jserv.JServConnection.processRequest(Compiled Code)
at org.apache.jserv.JServConnection.run(Compiled Code)
at java.lang.Thread.run(Compiled Code)
Please let me the resolution,,,
Thanks
Sumit

Correction:
you need to escape the & character in your XML file by using & instead of using & directly.

XI 3.0 - XML - IDOC inbound scenario via ftp UTF-8 character encoding

Hi Everyone,
I'm having difficulties with a particular scenario. I receive via the ftp adapter xml files which have a header indicating UTF-8 coding. In SXMB_MONI, i see the cyrillic characters and after mapping the target message payload as well have readable cyrillic characters. The problem comes when i have the SAP-side check the idoc that posted in their system. They see gibberish (i.e ##### #### ### #').
I have already tried changing the XSD definition of the xml to UTF-8 however upon import it automatically changes it to ISO-8859-1. I've tested sending the xml file to XI with an ISO-8859-1 coding header and in SXMB_MONI it's gibberish as well. So i've elminated that from possible problems.
i have checked SM59 on the receiving system and unicode is checked as well.
where could the problem possibly be?
Thank you,
Kent

Hi,
Thank you for the quick reply. however that did not solve it. I believe the Cyrillic character set lies in the UTF-8 set. i mentioned about the ISO to elmiinated its possibility and the problem i face when importing an XSD definition as it automatically changes the encoding to that set. I have confirmed that it should be UTF-8.
I have isolated the problem to between the XI box and the SAP receiving box. in SXMB_MONI, up to the call adapter part, the payload shows the correct characters. upon checking it in the receiving system at tcode "we02", the value is all gibberish.

UTF/Japanese character set and my application

Blankfellaws...
a simple query about the internationalization of an enterprise application..
I have a considerably large application running as 4 layers.. namely..
1) presentation layer - I have a servlet here
2) business layer - I have an EJB container here with EJBs
3) messaging layer - I have either Weblogic JMS here in which case it is an
application server or I will have MQSeries in which case it will be a
different machine all together
4) adapter layer - something like a connector layer with some specific or
rather customized modules which can talk to enterprise repositories
The Database has few messages in UTF format.. and they are Japanese
characters
My requirement : I need thos messages to be picked up from the database by
the business layer and passed on to the client screen which is a web browser
through the presentation layer.
What are the various points to be noted to get this done?
Where and all I need to set the character set and what should be the ideal
character set to be used to support maximum characters?
Are there anything specifically to be done in my application code regarding
this?
Are these just the matter of setting the character sets in the application
servers / web servers / web browsers?
Please enlighten me on these areas as am into something similar to this and
trying to figure out what's wrong in my current application. When the data
comes to the screen through my application, it looks corrupted. But the asme
message when read through a simple servlet, displays them without a problem.
Am confused!!
Thanks in advance
Manesh

Hello Manesh,
For the database I would recommend using UTF-8.
As for the character problems, could you elaborate which version of WebLogic
are you using and what is the nature of the problem.
If your problem is that of displaying the characters from the db and are
using JSP, you could try putting
<%@ page language="java" contentType="text/html; charset=UTF-8"%> on the
first line,
or if a servlet .... response.setContentType("text/html; charset=UTF-8");
Also to automatically select the correct charset by the browser, you will
have to include
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> in the
jsp.
You could replace the "UTF-8" with other charsets you are using.
I hope this helps...
David.
"m a n E s h" <[email protected]> wrote in message
news:[email protected]...
Blankfellaws...
a simple query about the internationalization of an enterpriseapplication..
>
I have a considerably large application running as 4 layers.. namely..
1) presentation layer - I have a servlet here
2) business layer - I have an EJB container here with EJBs
3) messaging layer - I have either Weblogic JMS here in which case it isan
application server or I will have MQSeries in which case it will be a
different machine all together
4) adapter layer - something like a connector layer with some specific or
rather customized modules which can talk to enterprise repositories
The Database has few messages in UTF format.. and they are Japanese
characters
My requirement : I need thos messages to be picked up from the database by
the business layer and passed on to the client screen which is a webbrowser
through the presentation layer.
What are the various points to be noted to get this done?
Where and all I need to set the character set and what should be the ideal
character set to be used to support maximum characters?
Are there anything specifically to be done in my application coderegarding
this?
Are these just the matter of setting the character sets in the application
servers / web servers / web browsers?
Please enlighten me on these areas as am into something similar to thisand
trying to figure out what's wrong in my current application. When the data
comes to the screen through my application, it looks corrupted. But theasme
message when read through a simple servlet, displays them without aproblem.
Am confused!!
Thanks in advance
Manesh

Quotation marks display as &quot in web pages, I'm using Unicode UTF-8 character encoding.

On many web pages, where a quotation mark character should appear, instead the page displays the text &quot. I believe this happens with other punctuation characters as well such as apostrophes although the text displayed in these other cases is different, of course. I'm guessing this is a problem with character encoding. I'm currently set to Unicode (UTF-8) encoding. Have tried several others without success.

Here's a link where the problem occurs. Note the second line of the main body of text.
http://www.sierratradingpost.com/lp2/snowshoes.html
BTW, I never use IE, but I checked this site in IE and it shows the same problem, so maybe it is the page encoding after all rather than what I thought.
In any case, my thanks for your help and would appreciate any solution you can suggest.

OracleXMLQuery fails with invalid UTF-8 character

All -
While using OracleXMLQuery API to pull the data back as a DOM. The internal parser has a fatal error with invalid UTF-8 data stored in the XML data.
Is it possible to use the setXSLT() method to transform the data before the DOM is attempted to be built. Or some other method within the OracleXMLQuery API to alter the invalid XML data before an attempt is made to parse it?
Note: The database will have non-UTF-8 data; Presently beyond our control.

Hi,
Are the files from the Java-CD fully readable and fully copied, for instance the java-dumpfile ?
Ensure JVM settings of note # 716604 area applied. Also, is connect possible to database by 'configtool' or does it throw an error ?
Br,
Javier

SAX FATAL:Unconvertible UTF-8 character

Similar Messages

Maybe you are looking for