dump persistence records

According to the escalation engineer:

 

 

> I've verified that the LTM is returning correctly formated XML data

 

> while with and without persistence information stored on the LTM. The

 

> customer's packet traces also show that the application buffers the

 

> LTM response and after the data is feed to the XML parser, the XML

 

> parser claims that the returned data is invalid. The data in the

 

> customer's traces are near identical to the XML output from my tests.

 

> Most likely the XML serializer is not able to parse the AoA which

 

> results in the error that they are seeing and if this is the case, this is a limitation of the XML serializer, not a fault of the product. The customer should verify that the XML serializer is able to handle the returned data.

 

 

The decrypted C511568.icontrol.txt file definitely shows well-formed XML being sent in response to the POST request that's submitted to /iControl/iControlPortal.cgi, up to the point where the client system issues a RST response to terminate the TCP connection. I'm not sure what an "AoA" is, but it seems to be the case that the XML serializer used by Visual Studio is not a happy camper when it receives it.

 

 

Bottom line: this seems to be a Microsoft Visual Studio issue, not a BIG-IP LTM iControl problem.Respectfully,