On Thu, Mar 23, 2023 at 01:24:16AM -0700, Agustina Martinez wrote:
> Thanks a lot for chipping in. All that you have described is exactly what
> is happening. To give some more details:
>
>- There is the single big transaction being built up, and it does not
>save until all the items in
Hi Mark,
Thanks a lot for chipping in. All that you have described is exactly what
is happening. To give some more details:
- There is the single big transaction being built up, and it does not
save until all the items in the collection have been processed.
- My task implementation is
Interesting. It sounds to me like there are two problems here, with a
common source:
o a (potentially) gigantic transaction is built up over a sequence of
operations which should be unrelated;
o a (potentially) gigantic queue of events which should be unrelated
is built up within the
ject: [dspace-tech] Re: DSpace 7.5 intermittent errors with patch operations
Hi Tim,
Many thanks for the hints. Yes, I can confirm now that the issue was completely
unrelated to CORS. Unfortunately there were no errors at all in any of the
backend logs regarding this other than a request timeout
Hi Tim,
Many thanks for the hints. Yes, I can confirm now that the issue was
completely unrelated to CORS. Unfortunately there were no errors at all in
any of the backend logs regarding this other than a request timeout.
I have managed to track down the issue and it was quite a worrying one,
Hi Agustina,
If you are sure it's not a CORS policy error, then I'd recommend checking
the backend logs. That "500 (Internal Server Error)" might also be logged
in dspace.log or tomcat logs. If so, there may be more information there to
help out. If it's reproducible semi-easily, you could
