Differentiating license issues with connection issues

Comienza en RemoteMatlabProxyFactory.java:176 y sigue cómo los tiempos de espera de la creación del proxy se manifiestan en el código fuente de matconsolectl. Reproduce el caso de agotamiento de licencias si es posible, compáralo con un fallo de red e identifica si está disponible el mensaje del gestor de licencias de MATLAB; se considera terminado cuando los dos tipos de fallo se pueden distinguir o la limitación está documentada.

We're running matconsolectl in a server job and using a corporate license pool.
Sporadically, we're getting this exception:

Exception in thread "main" matlabcontrol.MatlabConnectionException: MATLAB proxy could not be created in 180000 milliseconds
at matlabcontrol.RemoteMatlabProxyFactory.getProxy(RemoteMatlabProxyFactory.java:176)

I suspect that this is caused by being out of matlab licenses, but as far as I can tell from the matconsolectl source code, it does not have any special handling of license issues compared to e.g. network issues. Or am I misdiagnosing this and license errors will not get MatlabConnectionException timeouts?

It would be really nice if one could get the error message we get when running matlab directly, i.e.

"License checkout failed.
License Manager Error -4
Maximum number of users for MATLAB reached.
Try again later."

I'm not sure where to start looking for the above output though, so not sure how to fix it (if this really is the issue that I think it is)