blade initialization step freezes without any error message when the report directory can't be created
The blade initialization phase freezes without any error message, although all network settings are correct (see clif.filestorage.host and jonathan.connectionfactory.host properties when managing a distributed CLIF test plan). This occurs for a blade deployed in a CLIF server where the target directory for the measurement reports is not correct, i.e. does not exist and can't be created (most probably because of insufficient access rights).
This situation should result in getting an error message instead of silently getting stuck.
Note: consider setting the clif.filestorage.dir system property if you don't have right access to the default target report directory.