Hi

The next distribution update is expected within a couple of weeks.

In case you prefer to implement your own ARI, we recommend you to try keeping the Java component (i.e. the proxy adapter) and implement the protocol defined in
DOCS-SDKs\sdk_adapter_remoting_infrastructure\doc\ARI Protocol.pdf
in your own remote component.

However, as you suspected, the Java component has the same behaviour as the remote component, with respect to failure management. In synthesis, there is no recovery from problems in the communication between the proxy and the remote component.
In fact, in most cases, losing even a single update on the Data Adapter prevents the Adapter from honouring the interface contract with Lightstreamer Server.
So, whenever the connection is lost, the proxy Adapter makes the whole Server close, so as to leave to the clients all recovery decisions (assuming that a different Server is available in the cluster).
Note that, while on the Remote Adapter side there may be custom code to be preserved from a process close (as in your case), on the Server side, where the Proxy Adapter is running, this is not the case, unless other adapters are running. Only in the latter case (i.e. when other adapters are running), the Proxy Adapter behaviour may be unacceptable.

Only by coding your own Data Adapter in Java you can implement all the recovery strategies that your specific environment allows.

Dario