“Premature end of file” while mapping runtime cache refresh

July 14, 2009 at 3:00 am

[] [] [] [] [] [] []

  1. OutOfMemory Exception in Message mapping RuntimeSymptom Message mapping throws an OutOfMemory exception and it takes so much time to complete the execution, in spite of having a small payload. Other terms ESR, CE, SAP NetWeaver CE, PI...
  2. Error in Full Cache Refresh on DB2 Z/OS platformSymptom Full cache refresh does not works on PI system with DB2 database on Operating System Z/OS During full cache refresh, a deadlock occurs on the database and J2EE engine needs to...
  3. Unable to activate message mappingSymptom When a message mapping uses standard function JDBC lookup or when the number of mappings within a message mapping is very high, error occurs during the activation of the message mapping....
  4. NetWeaver BPM: Mapping contains errorsSymptom The Problem view shows an error and there are exceptions in the error log for a mapping but the mapping editor doesn’t show the error. Other terms Galaxy, SAP NW BPM,...
  5. Configuration of A2A PCIMs with mappingSymptom An Aris Process Component Interaction Model with two internal Process Components (A2A PCIM) and a connection with an Operation Mapping is transferred to the PI Directory. After configuration of the process...
  6. XI Runtime: Pipeline ID “Sender” is determinedSymptom The application client includes an XI message that has the pipeline ID “Sender” instead of “Receiver”. Therefore, this message is sent to the central XI and encounters an error. The message...
  7. PI archiving – Messages are deletedSymptom After the upgrade to 7.10 or 7.11, you use the switch procedure. If PI messages are flagged for archiving and only the inbound version is to be archived, the system does...
  8. Netweaver BPM: IllegalArgumentException in notificationsSymptom The start of a process or the instantiation of a human task fails with the following exception: java.lang.IllegalArgumentException: parameter RoleUserMap must not be null! at com.sap.bpem.tm.notification.RecipientsManager.getRecipients(RecipientsManager.java:89) at com.sap.bpem.tm.notification.RecipientsManager.getSubstitutingRecipients(RecipientsManager.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)...

Symptom

During the cache refresh of mapping runtime cache following error appears in defaultTrace:
Processing HTTP request to servlet [MappingCacheRefresh] finished with error. The error is: javax.servlet.ServletException: Attempt to parse XML document for the cache update of the imported archive failed at com.sap.aii.ibrun.web.mapping.MappingCacheRefreshServlet.doPost(MappingCacheRefreshServlet.java:96)
[...]
Caused by: org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
The refresh is nevertheless successful afterwards.

Other terms

Cache Refresh, Mapping Cache, SAP NetWeaver, Process Integration, SAP NetWeaver Process Integration
Reason and Prerequisites

The exception is caused by a programming error. If this error occurs a fallback implementation is used and the refresh is successful in spite of this error.
Solution

Correction is included in SP 9 of PI 7.10. Apply the SP in order to avoid the error.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment