DSpace 9.2: Submission Save / Autosave hangs after longer submission process

[Дмитрий Черных]

Hello everyone,

after upgrading one of our repositories from DSpace 9.1 to 9.2, we started receiving user reports about intermittent issues during the submission process.

Symptoms:

• When a user clicks Save in the submission UI, the caption changes to “Saving…” and stays in that state indefinitely.

• In some cases, the same behavior happens during autosave — the UI also shows “Saving…” and never recovers.

• The page must be refreshed to continue working.

• After refresh, some of the recently entered metadata may be lost.

Important detail:
Based on user feedback, this usually occurs when a user spends around 10 minutes editing metadata fields before clicking Save.  

These issues did not occur in version 9.1.

Environment / configuration:
OS: Debian 13
PostgreSQL 17
Solr 9.10.0
OpenJDK 21.0.9
Node.js v22.14.0
Tomcat 10
Apache HTTPD as reverse proxy

Questions:

1. Is this a known issue in DSpace 9.2, especially related to longer metadata editing sessions?

2. Were there any changes to authentication, XSRF handling, autosave, or submission save logic in 9.2 that could cause this behavior?

3. Has anyone observed similar behavior where Save or autosave hangs intermittently and data is partially lost after a page refresh?

Any pointers or insights would be greatly appreciated.

Best regards,
Dmytro

[DSpace Technical Support]

Hi Dmytro,

As of today, I've not heard of others encountering this.  But, it's still possible we'll receive other reports which could narrow down the issue.

In any case, I would recommend looking first for some underlying errors *when the hanging behavior occurs*.  This would require reproducing the behavior on your end, and looking for errors in either the User Interface or backend logs as described in our Troubleshooting guide: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error

Usually when the user interface "hangs", there's some sort of behind-the-scenes error or issue that has occurred.  If you can find that, it may provide more details as to why this is occurring for you, and whether it's something buggy in DSpace itself, or maybe something buggy in a specific configuration or customization.

Tim