Quantcast
Channel: SCN : Popular Discussions - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 971

Empty Message Handling - SAXParseException: Content is not allowed in prolog

$
0
0

Hi All,

 

I am using ignore option of Empty Message Handling in receiver file adapter to avoid creation of 0 byte files. But the output payload is having root message, so it creates empty output file with zero byte size.

And as mentioned in mentioned in SAP Note 0000821267 - FAQ File Adapter, there are 2 solutions i.e. Java mapping and use of StrictXml2PlainBean.

I referred below links also and created java mapping.

http://scn.sap.com/thread/3162134

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/04/17/file-receiver-adapter-better-utilization-of-handle-empty-message-feature

 

At OM level it is generating blank output at the target.

It is removing the root tag and avoids the output file creation but the receiver CC channel is throwing below error.

 

“Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):'org.xml.sax.SAXParseException: Content is not allowed in prolog.'”

 

Also CC audit log shows message "Write to file <DIRECTORYPATH\FILENAME> as text (encoding UTF-8) size 1 bytes." 

I am trying to figure out the cause of 1 bytes size.

 

Please let me know your thoughts and if someone has faced similar issue, pls provide inputs.

 

Regards,

Pranil.


Viewing all articles
Browse latest Browse all 971

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>