The eHealth initial mapping in SPECTRUM fails with the following error ?Initial mapping request failed" (Legacy KB ID CNC TS28405 )

Document ID : KB000052106
Last Modified Date : 14/02/2018
Show Technical Document Details
This issue is resolved in ehealth 6.1.

Related Issues/Questions:
The eHealth initial mapping in SPECTRUM fails with the following error "Initial mapping request failed"

The eHealth initial mapping in SPECTRUM fails with the following error "Initial mapping request failed: partial success: X elements had been mapped before receiving the following: eHealth mapping error: Failed to retrieve ELEM_TYPE_LANWAN details from mapping service."


 


The following errors can be see in the stdout.log file:


 


Details by UID for elements of type: ELEM_TYPE_LANWAN:


Jul 29, 2008 4:20:38 PM - MappingTask::getDetailsByUid could not retrieve list due to Exception:


AxisFault


 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException


 faultSubcode:


 faultString: org.xml.sax.SAXParseException: The element type "soapenv:Envelope" must be terminated by the matching end-tag "</soapenv:Envelope>".


 faultActor:


 faultNode:


 faultDetail:


            {http://xml.apache.org/axis/}hostname:stl-btraccp01


 


org.xml.sax.SAXParseException: The element type "soapenv:Envelope" must be terminated by the matching end-tag "</soapenv:Envelope>".

.

Problem Environment:
SPECTRUM 8.1
eHealth 6.0
eHealth Integration

Causes of this problem:

This is due to a bug in Apache on the eHealth server.  The Apache version is upgraded in 6.1 to resolve this issue.  The problem is that we are sending a request that is somewhere in the range of 8188 bytes long.  Apache has a max packet size of 8188 and a max read size of 8186 so it accepts the packet but cuts off the last two characters (which are meant to close the XML element).


 



Additional Information:
Workaround: If you turn on Mapping Information logging in the OneClick debug you can see what device is being processed at the time of the error. IF you discover one new element, or delete an element on that device in eHealth, the error will go away (for that device). You may have to repeat this procedure for other devices during the eHealth mapping.


(Legacy KB ID CNC TS28405 )