Hi Rick
Any idea why this happens and any way I can trace. It happens intermittently but quite often. (if that makes sense 😃 )
Single Instance Com Invocation failed: Thread was being aborted. - /syncorderstatus.api?instancing=single
The instance seems to run ok but this error happens when it completes.
No issues if I don't run as a single instance.
Thanks Rodney
What does the Log say?
+++ Rick ---
Just to be sure I took a quick look to make sure something didn't break in the v7 refactoring to binary output and I don't see anything failing with load testing.
Here's what I see:
Also tried this with the ASP.NET Module (the above is with the .NET Core server).
I did notice that the single instancing code hadn't been updated to the new binary processing, so updated that so the code for single instancing now uses the same processing as non-single instance code. However, the old string based code was working just fine as well.
I've pushed up the updated servers in Web Connection Experimental (v8.1.3)
+++ Rick ---