I have a problem when saving large documents (on some databases > 5 MB, on others > 10 mb).
Here’s the procedure:
Front-end is sending a request.
Back-end recieves the request and tries to save it.
The save method finishes but the document ID is null.
The save procedure is actually finished okay, the document is saved and it has its own ID. It feels like the save method finishes before its actually done and the save needs some time to save a document this large.
USE KEYS '24b49e61-2043-4b68-bc7f-a99be9f0ae1a'
This query is taking a long time to finish.
Sometimes I also get a timeout exception (Please see Image 2). Images 3 shows the request is OK (200) but the ID is null. (File has 9.63 MB) Image 4 shows the same requests but with a smaller file (1 MB). This time I got the id.
I did, in the UI it will execute the query in ~ 200 ms, but it doesn’t render the result for 10-20 seconds, for example a file that is 7mb. When trying the same query through my app, the query will always timeout for larger files. Tried raising query timeout with no success.
@jspnvk - When you are running the query in the UI, which output format are you using? JSON text? Tables? Rendering large documents in the UI can be time consuming, though usually the Tables are the most efficient.
Also, did you try running against the query service REST API? (http://:8093/query/service?statement=select …)
I just tried REST API query service and i was able to get the file, but it took ~4 seconds, as opposed to the 200ms that the UI is reporting. As i understand, this is well under the default timeout interval, so the question remains as to why it’s impossible to get the document through my app, but the query executes fine through the UI and query service.
Yes, there were timeouts because threads gave up before data from CB arrived. Any timeout fixes we tried failed, because they were ignored. Both Spring and CB failed to document how to configure timeouts properly.