[BUG] Elastic.Apm.AspNetFullFramework crashes on some SOAP requests to ASP Net Web Service

APM Agent version

Elastic.Apm.AspNetFullFramework 1.16.1

Environment

C# ASP NET Web Service

.NET Framework 4.8

Describe the bug

Some SOAP requests (not all, just some) to ASP Net Web Service crash if I have agent enabled in web.config. All I did was integrate agent into our old Web Service. Could be something wrong with SOAP request (syntax, etc.)? But other clients (Java, etc.) have no problems calling this Web Service for several years.

Exception message: System.Web.Services.Protocols.SoapException: There was an exception running the extensions specified in the config file. ---> System.InvalidOperationException: Either BinaryRead, Form, Files, or InputStream was accessed before the internal storage was filled by the caller of HttpRequest.GetBufferedInputStream. at System.Web.HttpRequest.GetEntireRawContent() at System.Web.HttpRequest.get_InputStream() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() --- End of inner exception stack trace --- at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)

[sabiland]

I have attached txt file with 9 separate XML SOAP requests. Nothing inside data is sensitive (enough), so I didn’t modify any data. That being said, still try to keep this data private.

EDIT: Now that the issue has been confirmed and solved, I am removing XML SOAP examples. Not that anything could be done with them, but just for any case. If someone would still need samples, they can contact me.

[sabiland]

Vau great 👍! I would probably never be able to debug this (to think that size of the XML request would be the problem) 😆.