The Aduio Encoding Problem

I came up against this sometime ago with a few iM projects that I sent to iDVD (spinning beachball, long wait for audio encoding, etc.)
I kept up with threads on here talking about possible problems with CBR MP3's and it seemed to centre around iDVD 6.0.2
For the first time in a few weeks I burnt an iM project to DVD using iDVD and didn't run into the Encoding Audio problem although, admittedly, the project was probably the most simple in terms of audio I've done, and, did not include any MP3's
The question I have is; is this still a problem for iDVD, as, I've noticed it's upgraded to 6.0.3 (791)?? I've been advising some friends on iM and burning using iDVD and would be nice to tell them this issue is resolved / fixed...
Luke

iDVD 6.0.3
This update addresses compatibility for accessing Aperture 1.5 content in iDVD.
iMovie HD 6.0.3
Updating iMovie HD 6.0.2 to 6.0.3, this update addresses compatibility for accessing Aperture 1.5 content in iMovie. It also improves overall stability and addresses a number of other minor issues.
iMovie HD 6.0.2
Updating iMovie HD 6.0.1 to 6.0.2, this update to iMovie HD 6.0.1 addresses issues with PAL audio and displaying iLife Sound Effects automatically in its iLife Media Browser. It also improves overall stability and addresses a number of other minor issues.
iMovie HD 6.0.2
Updating iMovie HD 6.0.0 to 6.0.2, this update addresses issues with Ken Burns rendering performance, scrubber bar editing performance, theme image quality, PAL audio, and displaying iLife Sound Effects automatically in its iLife Media Browser. It also improves overall stability and addresses a number of other minor issues.
They really don't say, do they? Sue

Similar Messages

Has Apple fixed the audio encoding problem?

As many other people seems to have experienced before me, iDVD6 stops working when encoding audio. Everything works before that step but when it reaches the "Audio Encoding" sequence iDVD stops working. Did Apple fix the problem? What else can we do?
Thanks for any reply.
Frank
iMac G5 Mac OS X (10.4.5) PowerMac G4

I followed your advice and restarted at 6:00 pm last night - this morning it was still going on - over 13 hours! The funny thing this time is that I got the 'rainbow ball' encoding audio at the beginning of the 3rd step, 'Processing movie' after only 1-1/2 hour. The last time I burned the same project, I got the 'rainbow ball' encoding audio message at the end of the 3rd step - in other words, it had processed the entire movie (which took 6 hours) and then began the encoding audio phase. I'm letting it run while I'm at work, but do you think there might be something else going on?
Here are some facts which apply to both times that I have tried burning the DVD project:
1. I have iMovie project (26Gb) on my external drive with about 15 Gb available space
2. and the iDVD project is on the internal hard drive with about 50 Gb of available space
The reason I moved the iMovie project to the external drive was because I would have only had about 24 Gb of available space if I left it on the internal drive (less than the movie itself).
Which drive is doing all the encoding and needing the most space - the internal or the external? I was assuming it was the internal drive. Should I move the iMovie project back to my internal drive and start over?
Thanks again - I'm a new member of this site and so far, it has been very helpful and informative!

Character encoding problem by Gmail set up as exchange account on IOS mail

It was maybe asked before but I could not find any solution. If someone can help I would appreciate it...
If I set up my gmail, which I use very heavily, as Gmail on the IOS mail installation it would be set up as IMAP and does not push the emails. If I choose it to install as exchange account via m.google.com everything is OK and I get my mails instantly. But the way over exchange disturbs because of the character encoding problem. IOS mail does not show me the turkish or some german characters like "ü" and the mail is almost not readable... By version 1 also as IMAP there is no problem with the characters but I must start IOS mail everytime to see if I have new mail...
Does anyone know a solution for it?
Thanks...
Mel

But I cannot set the the gmail app as standart email program, or? I mean if I want to send a page on safari and click send via email, the mail.app would start and not the gmail.app.... I am using Iphone since a few weeks and as far as I know a customisation is not possible.

How to detect the root cause of XML encoding problem ?

Hi,
I need to identify the exactly root cause of error when parssing a XML ( ISO-8859-1 encoding) problem.
How can I do this using JAVA ?
regards
ICP

Hi dekassegui,
Thanks for your response
The error is an error from Oracle HTTP adapter servlet. The message error is : "oracle.xml.parser.v2.XMLParseException"
My intention is to verify the data before thats receieved by the adapter and the servlet.
I did my own servlet extending the orgirinal servlet to show and log the entire received content. The content looks "OK".
Now I would like to check a possible special character or symbol unsupported by enconding.
The Input data is aware of my control. But if the error could be detected, message senders will correct this.
My major problem is to ensure what is the root cause of the error.
regards,
ICP

Problems setting the charset encoding via jdbc

Dear list,
I would like to know if/how its possible to set the character encoding via the jdbc string, with the oracle thin driver client (classes12.jar).
Microsoft SQLserver for example supports the addition of a charset="utf-8" for example in the jdbc url.
Please could tell me how/if this is possible.
A pasted example would be much appreciated..
ben bookey

This bug will be fixed with SP20.
Regards
Stefan

How to specify the charatcer encoding for the parametes Content-Disposition

I want to download a file with chinese name .
response.setHeader("Content-Disposition","attachment; filename=" + fileName);
the above part of code is working fine for english file names. but i am facing problem when i try to get file with chinese name .
The pop up window is not defaulting with the chinese name .
When i searched for net , in one rfc it was specified how to do that one.
http://www.faqs.org/rfcs/rfc2184.html.
I tried it but .. could not able to solve the problem.

Hi,
Am facing similar problem with russian and japanese characters in file name.
I tried the UrlEncoder.encode(filename, "utf-8') api to encode the file name. This worked fine with IE but firefox and safari shows junk for japanese/russian characters.
Anyone having an idea abt this?
Thanks,
Kapil

Encoding problems in email while on Windows Mail app

Hello.
I have a question concerning email and encoding problems in the Windows Mail App in Windows 8.1. I have encountered a problem with an email I received, while reading, I see strange ASCII characters in one email. I have never encountered it in
my web browsers nor Gmail, just the Mail App.
I was referred to come here when I had asked a similar question there:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-ecoms/strange-foreign-ascii-characters-appearing-in/911f8a44-c302-4fa1-bcaa-3297b32d9120
I don't know which forum to go to so I picked here.
Is there any way that it can be resolved. I tried to troubleshoot, nothing worked; I even synched, to no avail.
I look forward to a response.
JB

Hi JB,
The responder on answers was a bit confused. The MSDN forums are for developers to discuss writing their own apps. We cannot help with problems using Windows or its built-in apps.
If the folks on answers cannot help then you may need to open a support incident. See
http://support.microsoft.com , or the folks on answers may be able to direct you to the specific page for the Windows Mail app.
--Rob

File adapter ISO-8859-1 encoding problems in XI 3.0

We are using the XI 3.0 file adapter and are experiencing some XML encoding troubles.
A SAP R/3 system is delivering an IDoc outbound. XI picks up the IDoc and converts it to an external defined .xml file. The .xml file is send to a connected ftp-server. At the remote FTP server the file is generating an error, as it is expected to arrive in ISO-8859-1 encoding. The Transfer Mode is set to Binary, File Type Text, and Encoding ISO-8859-1.
The .xml file is encoded correctly in ISO-8859-1, but the problem is that the XML encoding declaration has the wrong value 'UTF-8'.
Does anybody know of a work around, to change the encoding declaration to ISO-8859-1 in the message mapping program?

An example of the XSL code might be as follow:
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method='xml' encoding='ISO-8859-1' />
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>

Media Encoder Problem

I am using Flash CS 4, If I attempt to file>import>import video, the import video window/dialog box opens, if I browse and select a AVI.file I receive a dialog box telling me it is in the wrong format and to use the Launch Adobe Media Encoder button to convert to proper format. This is where problem starts.
An Adobe Media Encoder Debug Event dialog box opens, it states that "Adobe Media Encoder has encountered an error", ..\..\Scr\Init.cpp-42
the only option is to select a continue button, then an Adobe Media Encoder dialog box opens stating that "adobe media encoder has encountered a problem and must close. It wants to report the issue to Microsoft, but that doesn't help me start or repair my problem. I have created a 3 page PDF of screen images which shows the sequence of dialog boxes and messages, I have tried to locate error data files in application data files, I can find the folder but it does not contain any error txt files.
Can any one Help me with this issue, any way I attempt to open Media Encoder the results are the same.

I've been very fortunate to have a lot of hi-def video work the last three months and the Media Encoder is literally making me think that Premiere CS4 is really more of a hobby program. I spend a third of my time watching the encoder stop, viewing encoded files that don't work. I updated to 4.0.2 and it is worse. I think Adobe really needs to address this problem. Premiere is a great tool and its ability to import Sony Hi-def XDCAM footage is really a nice thing, very helpful, but what good is it when you spend so many hours watching your finished video get crashed in the encoder? I have tried a lot of things and at this point one pass on the FLVs for client reviews seems to be the best I can do. I have a great computer with a quad CPU and lots of ram but I really think Adobe is not addressing those of us that want to use the tool to make a living that are finding it a really bad encoder and would love to hear any ideas on what I might be able to do.
BTW--typical project is 6-7 min. long with about 100-125 clips. I had a lot of problems also with Premiere CS4 crashing and not allowing me to open files but I used embeded sequences to stop the crashing. If I didn't spend so much time finding workarounds on CS4 I could really make a good living. BTW--the Sony EX1 is a really great HD camera.
Leo

Encoding problem after File Content Conversion

Hi SAP gurus!
we're about exporting debitor data via PI into CSV files. Therefore we use a mapping to an intermediate structure. In the receiver file adapter a file content conversion is done into the target CSV format.
We have a lot of data with eastern europe characters. Right after the mapping, everything is fine. All characters are processed correctly. After the file content conversion, the files written on the target system contain "?" instead of the special characters.
Does anybody have any hint to fix this problem? We already tried to change the "file.encoding" parameter, but hasn't helped.
Thanks in advance for your support!
Cheers,
Matthias

Hello Satish,
thanks for your reply.
First, I have to explain, that the sender side isn't done by file adapter but IDoc adapter. So I cannot change the encoding on sender side.
Both on IDoc and file side, the data is ok. Only when inserting the file content converion, the files become corrupted.
Without using the FCC, tjhe target files are stored as UTF-8. When using FCC the files are stored as ANSI. (I tested this by opening the files in notepad and performing "Save As")
Do you have further ideas?
Cheers,
Matthias

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Transformer transformer = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Yes\" />\n")
                 .append("</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("initial xml = \n" + xmlStrBuf.toString());
        try
            //Test1: Use the transformer to ouput the xmlStrBuf.
            // This shows the xml encoding result from the transformer which will change to UTF-8
            tFactory = TransformerFactory.newInstance();
            transformer = tFactory.newTransformer();
            StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
            System.out.println("Test1 result = ");
            transformer.transform( ss, new StreamResult(System.out));
            //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document. the encoding becomes UTF-8
            DOMSource source = new DOMSource(document);
            StreamResult result = new StreamResult(System.out);
            System.out.println("\n\nTest2 result = ");
            transformer.transform(source, result);
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
    public static void main( String arg[])
        XmlEncodingTest xmlTest = new XmlEncodingTest();
        xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Resoluci�n\">\n")
                 .append("Special charatered attribute test")
                 .append("\n</ELEM>")
                 .append("\n</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
        try
            //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
            //Test1: Use the transformer to ouput the xmlStrBuf.
            tFactory = TransformerFactory.newInstance();
            Transformer transformer = tFactory.newTransformer();
            byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
            StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
            ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
            Properties transProperties = transformer.getOutputProperties();
            transProperties.list( System.out); // prints out current transformer properties
            System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
            transformer.setOutputProperty("encoding", "ISO-8859-1");
            transformer.transform( streamSource, new StreamResult( xmlBaos));
            System.out.println("**** Test1 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new ByteArrayInputStream( xmlbytes));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document.
            DOMSource source = new DOMSource(document);
            xmlBaos.reset();
            transformer.transform( source, new StreamResult( xmlBaos));
            System.out.println("\n\n****Test2 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //xmlBaos.flush();
            //xmlBaos.close();
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
        finally
    public static void main( String arg[])
        XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
        xmlTest.performTest();
}

File encoding problem in solaris sparc

hi there,
I wrote a simple program to create a text file that with the content of japanese character that same way I wrote in Windows JP Platform.
However, the encoding is different from what window, oracle(solaris sparc) does.
this is very interesting that we view from oracle and its workd fine from Oracle which run on the same machine(solaris Sparc) .
I believe I missed out some setting for the internationalization for JDK in solaris, but I'm not familiar with solaris. Hence, I would like to seek is there one of you came across this before? Please help.
Here is the String.
\u6771\u9999\u91CC\u5357\u753A�T�W�|�T�|�P�O�P
Please note that 58-5-101 is double full width JP character.
The main problem is the "-" encoding for solaris. It changed to '?'
My env are,
-jdk1.3.1_03
-Solaris Sparc LANG=ja
pls feel fre to ask for more information if you need further details.
regards,
elvis
scjp

I don't fully understand what you're asking for, but I wonder if this might help : the default encoding of a Solaris machine is probably EUC (In Windows, this is SJIS). So you'll probably have to read the file using the EUC encoding. Have a look at InputStreamReader(InputStream in, String enc) where you can set the encoding of the input stream.
(Note that there is also a forum called 'Internationalization' at java.sun.com)

The real powerpoint problem

The reason for this question about powerpoint is that the image quality of the powerpoint became unacceptable once the powerpoint slides were re-created as TIFF files and imported into Final Cut, added to an existing video, then exported as an MPEG-2 file for creation as a looping video.
This led me to investigate DVD@access as a way to simply tell the DVD to play the video, then play the powerpoint, then start over. I figured that if the powerpoint played natively, the image quality problems would be solved, but maybe this is not possible.
Any ideas?
Steve

hi Steve, I realise this is a DVDSP3 thread but here's another approach I used some time back for some work slides. I did try and take the playable DVD approach with powerpoint so I will mention this first then let you know about another approach that I think is superior.
1) Powerpoint: as you say, the TIFF images from PPT are not up to your needs. Whether it is resolution or just obvious artifacts on the images when played out for a video_ts from after authoring from DVDSP3 for example. so.. try this:
• make your PPT up with builds and transitions as you wish. Set the slide viewing time to 5 seconds.
• export as a QUICKTIME movie using the ANIMATION CODEC. (not other ones you may have). This is important because you will have something approaching uncompressed that you can work with. (Optionally add CHAPTER MARKERS with FCP or QTPLAYER etc)
• Tweak your authoring title as you do in DVD SP3... then ENCODE this with DVDSP3 as you source. When this is finished erase/delete/purge the previous QT file.
• you may then add CHAPTER marks in DVDSP3 or BEFORE HAND in FCP or QTIME PRO for you slideshow navigation from most players.
• drawback is that other navigations functions such as DVD@access etc may not work. I have not used this.
• simply this works ok.. PLay out as a DVD5 title or from the host machine as a VIDEO_TS .. you get the idea. VLC etc etc
• this is also very cool for having the 'presentation' to your video ipod. Use composite cable to projector/beamer. Limited to 640x480 but has save me a few times when pc laptop fails.
OPTION#2: forget the DVD approach and use H.264/AVC instead as:
• prpare you .ppt as above.
• export as a QT movie using APPLE ANIMATION CODEC as above. This is a temporary file you will purge later.
• tweak the QT movie with the usual tools form FCS etc.... and add stuff you need for the fonal thing such as audio etc etc and voice over if you want that.
• then export as an H.264/AVC at the resolution you need for your show.. 1024x768 or less at around 1.5Mbs multipass is about right. Most windows low end laptops can play this with VLC or QT. Must use 'space bar" or pause to work through presentation with audience.
• advantages are tha you get visually the same look for far less storage space required and NO DVD .
• DVD chapter navigation is not possible of course , however this can be simply managed by invisible ACTION SPRITES to your H.264 MOVIE using tools from ADOBE. THe downside of this approach is that is can be tricky to do, but worth it.
That is essentially is.
Having said all that, my preferred method is to use APPLE KEYNOTE (iWORK '08) as a previous poster on your thread has stated. It is easy to use and performs what I have described above is an easy way using a similay technique under the covers.
 Keynote also permits presentations of varying resolutions up to HD or customisable resolutions. Does PPT do this?? I dunno.
Keynote also has many other goodies in it , especially voice over nd synchronisation of play out based on triggers I recall. HOwever it is not transportable to people that dont have KEYNOTE... (same as .ppt ).
anyway, this works or me. I am a greta fan of H.264.AVC.
hth
w

Encoding problem while reading binary data from MQ-series

Dear all,
we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
It seems to us that
1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
2. Both CCSID parameters are not used anyway in JMS-adapter
How can we solve this problem without changing anything on MQ-site?
Here is the stack-trace:
Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
    at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
    at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
    at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
    at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
    at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
    at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
    at java.lang.Thread.run(Thread.java:770)
Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
    ... 36 more
Caused by: sun.io.MalformedInputException
    at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
    at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
    at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
    at java.io.InputStreamReader.read(InputStreamReader.java:208)
    at java.io.BufferedReader.fill(BufferedReader.java:153)
    at java.io.BufferedReader.readLine(BufferedReader.java:316)
    at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
    at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
    ... 40 more
Any ideas?
Kind regards, Stefan

Hi Stefan,
for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
The second MTB, which does the XML-Wrapping, is configured like this:
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = application/xml
xml.conversionType = SimplePlain2XML
xml.fieldNames = value
xml.fieldSeparator = §%zulu§%
xml.processFieldNames = fromConfiguration
xml.structureTitle = payload
Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á). E1 is (different from ISO) an "ß" in 850.
Any ideas?

XML export encoding problem

Hi all,
I've got a problem when I export BW query data in xml format. I send the xml file containing query data to a BSP controller and read out the file using form fields. The problem is that some characters get 'damaged': german characters like 'äöüÄÖÜ' etc. or '' can't be received correctly. I assume that the query gets export in iso 8859-1 encoding and the BSP controller expects utf-8. Is there a possibility to change the export encoding of the xml document before it gets send to the BSP controller? Or is there other solution?
Thanks in advance,
Dominik

Hello,
The solution for this issue is before transferring the xml file convert it to xstring with proper encoding and then send iit to BSP,
you can use the following,
call function 'SCMS_STRING_TO_XSTRING'
regards,
karthik

The Aduio Encoding Problem

Similar Messages

Maybe you are looking for