Cloud Services (Extended Support) works for 20 minutes or so then fails

Andrew HB 321 Reputation points
2021-04-14T17:09:05.067+00:00

We have been migrating our Cloud Services (Classic) application to Cloud Services (Extended Support) and are having major issues with the application failing after 20 minutes or so after deployment. If I deploy the app after it has been deployed everything works fine for around 20 minutes and then the application fails with the following error: -

The data at the root level is invalid. Line 1, position 1.
at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, String res, String arg1, String arg2, String arg3)
at System.Xml.XmlUTF8TextReader.Read()
at System.Xml.XmlBaseReader.IsStartElement()
at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
at System.Runtime.Serialization.XmlObjectSerializer.IsRootElement(XmlReaderDelegator reader, DataContract contract, XmlDictionaryString name, XmlDictionaryString ns)
at System.Runtime.Serialization.DataContractSerializer.InternalIsStartObject(XmlReaderDelegator reader)
at System.Runtime.Serialization.DataContractSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

The Cloud Service is deployed using an osFamily="5" guest OS and uses the Thinktecture IdentityServer2 federated authentication middleware to control access between the application and the auth server.

There are 2 Cloud Services running identical OS and I have created them with a single instance each. I have been trying to solve this for 4 days and am at my wits end!

Any advice?

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
635 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Andrew HB 321 Reputation points
    2021-04-14T20:50:08.633+00:00

    so the time delay is related to a session a timeout, if use the app and just keep moving around it doesn’t fail so some kind of session timeout is occurring which is then causing “something” to fail in the asp.net pipeline. This all worked perfectly in the classic cloud environment so what is different about extended support that I need to consider?

    For example even though I only have a single instance of my web role what affect does the load balancer have on my requests if any? The old classic service had multiple instances so something must be different about this new environment.?

    0 comments