Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

Premature end of file - JMS Sender

$
0
0

Hi Gurus,

 

I've the following scenario: JMS Provider (WebSphereMQ) to IDOC (DEBMAS05). So, it's between AS400 (With MQSeries 6) and SAP ERP.


Steps:

  • When the client makesa modificationto a record,it generatesa message to aMQqueue. For example a new email address...

 

  • ThenI checkthat I havea message inthe appropriate queue XXXX.POLL.001.

 

  • I usethe "12" option,to work withthe message.

 

  • With "8"I canseethe message.


  • Here, the message istruncatedto view it.(has more than1024bytes). This is my firstquestion, SAP PItakesall data from the queue oronlythe first 1024bytes?

 

  • I have seen theMQqueue for the customer byanother program andthisis34598bytes.

 

  • In SAP PI, I've configured the sender channel at the "module" with the MessageTransformBean module. The key name is Plain2XML. Here, I built(usingparameters) the transformationto acomplexxml.


The beginning of module...



At the end of Module...

 

  • For example, some data like "ShippingData" is empty in the original message in the MQ queue. Here my second question, SAPPIdatatakes into account the"ShippingData"and transforms it intoemptyXMLelementsor do not takeinto account?


  • The JMS Sender Channel, take the message without problems..

 

  • I've opened the soap message created by the JMS adapter...

 

  • I usea program to seetheSOAPmessage(Notepad++)andI canseethat itis truncatedand containsthexmlstated in theJMSchannel.

 

  • Then, I see the Log Viewer to know the error...

 

The error message is the following:

 

  • When I go for details...

Tracing for additional info - MTSaxHandler.run:
Thrown:
org.xml.sax.SAXParseException: Premature end of file.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1476)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1078)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:513) 
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:744)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:128)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:543)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at com.sap.aii.mappingtool.tf7.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:273)
at com.sap.aii.mappingtool.tf7.rt.xparser.XParser.run(XParser.java:112)

 

  • As can be seenthe errorappears: "Prematureend of file.". Causing the errorin mappingthe elements. Anyone haveanyidea how toputparameter inJMSsenderchannelto takemorethan 1024bytesmessage.

 

Thanks a lot!




Viewing all articles
Browse latest Browse all 7030

Trending Articles



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