Closed stefanolsen closed 3 years ago
Thanks for the report, I added to out internal tracking system,
@lunchin: Maybe you could also replace Newtonsoft.Json with System.Text.Json in the future?
It should be using System.Text.Json
I tested it again. Newest packages still use Newtonsoft in Shell responses, which generates the same error with a large catalog node.
No I meant it should, we just fixed the issue, will be in package drop today
I have reported an issue that Newtonsoft should not be used in this scenario.
An alternative workaround for now (to AlllowSynchronusIO = true) is to increase the buffer that is used when async write is not possible, Like:
services.Configure
Fixed in EPiServer.Commerce.Core.14.0.0-inte-021024
I saw this error again today. In Assets gallery, when expanding a folder with many subfolders.
In the cms not commerce correct?
I think this is related to this
https://github.com/episerver/netcore-preview/issues/97#issuecomment-897533932
@lunchin: It was in CMS.
I am testing out a Commerce 12 installation, in which one of the catalog nodes contain more than 200 products, along with relevant sub-entries. When browsing this catalog node, the XHR-request fails with the below stack trace. When browsing any other (smaller) catalog node, the proper response is returned.
I have read that the quick-fix is to set AllowSynchronousIO to true. But I would prefer to have this block of code fixed to be completely async (as suggested in the exception message).
Build: