okhttps | 如艺术一般优雅，像 1、2、3 一样简单，前后端通用，轻量却强大的 HTTP 客户端（同时支持 WebSocket 与 | HTTP library

Instead of using server.useHttps, you can simply try creating a network security config, whitelist localhost and add it to your app.

First, create a network_security_config.xml and put it into your app's res/xml folder

Apparently, I was passing in the contentLength incorrectly. After assigning it to the length of the array returned by Base64.decode(encodedImage, Base64.DEFAULT), it worked!

Deadlocks are usually resolvable by retrying. Internally, the server does a inner-retry loop because usually deadlocks are transient and incidental, lasting a very short time. In your case you have constructed a case that will never succeed with any timeout that's equal for both threads. Deadlocks can be avoided at the application layer by avoiding multi-statement transactions when using the REST API. (which is what the Java api uses). Multi statement transactions over REST cannot be implemented 100% safely due to the client's responsibility to manage the transaction ID and the server's inability to detect client-side errors or client-side identity. Very subtle problems can and do occur unless you are aggressively proactive wrt handling errors and multithreading. If you 'push' the logic to the server (xquery or javascript) the server is able to manage things much better.

As for if its 'good' or not for the Java API to implement retries for this case, that's debatable either way. (The compromise for an seemingly easy-to-use interface is that many things that would otherwise be options are decided for you as a convention. There's generally no one-size-fits-all answer. In this case I am presuming the thought was that a deadlock is more likely caused by independant code/logic by 'accident' as opposed to identical code running in tangent -- a retry in that case would be a good choice. In your example its not, but then an earlier error would still fail predictably until you change your code to 'not do that' ).

If it doesn't already exist, a feature request for a configurable timeout and retry behaviour does seem a reasonable request. I would recommend, however, to attempt to avoid any REST calls that result in an open transaction -- inherently that is problematic, particularly if you don't notice the problem upfront (then its more likely to bite you in production). Unlike JDBC, which keeps a connection open so that the server can detect client disconnects, HTTP and the ML Rest API do not -- which leads to a different programming model then traditional database coding in java.

You are overwriting same file by passing same name,change it too file[] OR Pass as file1 and file2

port was the issue. Since I ran the Marklogic database using docker, I had to open the ports 8010-8013 as given in FAQ while running the docker container using the below statement

docker run -d --name=data-hub -p 8000-8013:8000-8013 marklogic:9.0-3.1-installed

You can implement a singleton helper class that keeps one OkHttpClient and cover all of your custom functionalities using this one particular client:

You should add an interceptor for okhttp something like this should work

How to handle auth0 403 error without adding specific code everywhere (Retrofit/okhttp/RxAndroid)