Unable to Reconfigure vSphere Replication. Caused by: java.net.SocketTimeoutException: Read timed out
search cancel

Unable to Reconfigure vSphere Replication. Caused by: java.net.SocketTimeoutException: Read timed out

book

Article ID: 415240

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

When running a vSphere Replication reconfigure from the VAMI (https://applianceIPorFQDN:5480), the task fails.

The Site Recovery Plug-in shows the vSphere Replication appliance as 'Not Configured'

The Site Recovery UI shows as the affected vSphere Replication as 'Not Connected'

Within the hms-configtool.log file in /opt/vmware/hms/logs shows the following 'java.net.SocketTimeoutException: Read timed out' error:

2025-10-15 20:56:39.803 ERROR com.vmware.hms.config.VrConfig [main] (..hms.config.VrConfig) [] | Failed to commit appliance configuration: [ msgId: com.vmware.vr.config.gene
ral_failure; value: null; errorStacktrace : com.vmware.vim.vmomi.client.exception.ConnectionException: https://vCenterIPorFQDN.local:443/lookupservice/sdk invoc
ation failed with "java.net.SocketTimeoutException: Read timed out"
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:265)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.setResponseError(HttpExchangeBase.java:362)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.invokeWithinScope(HttpExchange.java:59)
        at com.vmware.vim.vmomi.core.tracing.NoopTracer$NoopSpan.runWithinSpanContext(NoopTracer.java:120)
        at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:17)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.run(HttpExchangeBase.java:52)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:229)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:128)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:693)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:674)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:371)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:322)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:195)
        at jdk.proxy2/jdk.proxy2.$Proxy51.list(Unknown Source)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter.findRawServices(LookupServiceAdapter.java:326)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter.findServices(LookupServiceAdapter.java:309)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter.findService(LookupServiceAdapter.java:276)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter.getStsEndpoint(LookupServiceAdapter.java:242)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter$2.run(LookupServiceAdapter.java:128)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter$2.run(LookupServiceAdapter.java:1)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceBase.with(LookupServiceBase.java:83)
        at com.vmware.jvsl.lookupsvc.adapter.LookupServiceAdapter.getStsEndpoint(LookupServiceAdapter.java:124)
        at com.vmware.hms.apps.util.util.VrConfigAction.run(VrConfigAction.java:152)
        at com.vmware.hms.apps.util.App.run(App.java:103)
        at com.vmware.hms.apps.util.App$1.run(App.java:152)
        at com.vmware.jvsl.run.ExceptionHandlerRunnable$1.run(ExceptionHandlerRunnable.java:47)
        at com.vmware.jvsl.run.CheckedRunnable.withoutChecked(CheckedRunnable.java:19)
        at com.vmware.jvsl.run.ExceptionHandlerRunnable.withExceptionHandler(ExceptionHandlerRunnable.java:43)
        at com.vmware.hms.apps.util.App.main(App.java:149)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)
        at com.vmware.hms.config.vix.ApplianceCommandExecutor.command(ApplianceCommandExecutor.java:53)
        at com.vmware.hms.config.RemoteCommandExecutor.command(RemoteCommandExecutor.java:50)
        at com.vmware.hms.config.VrConfig.commitApplianceConfiguration(VrConfig.java:710)
        at com.vmware.hms.config.VrConfig.expressSetup(VrConfig.java:344)
        at com.vmware.hms.config.cli.command.ExpressSetup.run(ExpressSetup.java:59)
        at com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:347)
        at com.vmware.hms.config.cli.App.run(App.java:146)
        at com.vmware.hms.config.cli.App.main(App.java:206)
Caused by: java.net.SocketTimeoutException: Read timed out

Environment

vSphere Replication 9.0 +

Cause

When looking at the hms.log in /opt/vmware/hms/logs, you see a different value other than 120000 for the line: 'Set default vlsi client timeout to (ms)'

2025-10-20 03:05:56.238 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | HMS 9.0.2.17642 build-24168908 attempting to start...
2025-10-20 03:05:56.244 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Maximum heap size:    2147483648
2025-10-20 03:05:56.244 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Maximum PermGen size: -1
2025-10-20 03:05:56.244 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Config file location: /opt/vmware/hms/conf/hms-configuration.xml
2025-10-20 03:05:56.300 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | FIPS mode: false
2025-10-20 03:05:56.300 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Initializing Spring
2025-10-20 03:05:56.300 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Set default vlsi client timeout to (ms): 15
2025-10-20 03:05:56.300 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Set default vlsi client socket connect timeout to (ms): 15000
2025-10-20 03:05:56.301 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Set default REST client socket connect timeout to (ms): 15000
2025-10-20 03:05:56.301 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Set default REST client request timeout to (ms): 120000
2025-10-20 03:05:56.301 INFO  com.vmware.hms [main] (..vmware.hms.App) [] | Set default REST client connection request timeout to (ms): 120000

**The vSphere Replication appliance parameter 'hms-default-vlsi-client-timeout' has a default value of '120000'. Having a lower value set will cause issues reconfiguring vSphere Replication with vCenter

Resolution

Open a case with the Broadcom vSphere Replication team to assist in restoring the default value for parameter 'hms-default-vlsi-client-timeout'

Powered by Wolken Software