It's all about the answers!

Ask a question

Not able to accept changes due to the "Failed to acquire locks on requested sandboxes in 60000ms." exception


Ewa Stempel (111) | asked Apr 23 '15, 6:27 a.m.
 Hi,

I am running the following commands and receive the following error, when trying to accept the changes:

Commands:
lscm login -r <url> -u <username> -P <password> -n a 
lscm accept -r a -s "<source_name>" -t "<workspace_name>" -d "<path_to_local_dir>" -o 
lscm logout -r a

Error message:
com.ibm.team.repository.common.TeamRepositoryException: Failed to acquire locks on requested sandboxes in 60000ms.

at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postRegisterSandboxes(FilesystemRestClient.java:1947)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:600)

at com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:322)

at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628)

at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:328)

at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeErrorObj(JSONDeserializer.java:955)

at com.ibm.team.filesystem.client.internal.marshalling.ExceptionHandlingJSONDeserializer.deserializeErrorObj(ExceptionHandlingJSONDeserializer.java:128)

at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeException(JSONDeserializer.java:933)

at com.ibm.team.filesystem.client.internal.marshalling.EObjectJSONDeserializer.deserializeError(EObjectJSONDeserializer.java:71)

at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:267)

at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.java:221)

at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368)

at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311)

at com.sun.proxy.$Proxy1.postRegisterSandboxes(Unknown Source)

at com.ibm.team.filesystem.cli.core.util.SubcommandUtil.registerSandboxes(SubcommandUtil.java:950)

at com.ibm.team.filesystem.cli.core.util.SubcommandUtil.registerSandboxes(SubcommandUtil.java:943)

at com.ibm.team.filesystem.cli.core.util.SubcommandUtil.setupDaemon(SubcommandUtil.java:1216)

at com.ibm.team.filesystem.cli.client.internal.subcommands.AcceptCmd.run(AcceptCmd.java:107)

at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)

at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:535)

at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:349)

at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:125)

at com.ibm.team.filesystem.cli.client.internal.daemon.CommandLineClient.handleRequest(CommandLineClient.java:186)

at com.ibm.team.filesystem.client.internal.http.ProtocolSwitchingHttpHandler.handle(ProtocolSwitchingHttpHandler.java:46)

at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628)

at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Problem running 'accept':

Could not register sandboxes.


Would you happen to know how to resolve the problem?

Thanks,
Ewa

One answer



permanent link
Surya Tripathi (65017) | answered Apr 23 '15, 1:17 p.m.
 Looks like the path -d "<path_to_local_dir>"  in your command is potentially in use. Do you have another scm.exe process running? You can try terminating all scm.exe processes and SCM client application and try again. You may also have to reload your workspace in a different location and then accept changes. 

Comments
Ewa Stempel commented Apr 24 '15, 11:00 a.m.

 Hi Surya,


Thanks for your response.

Perhaps I should mention that I run these commands from Jenkins and I did check if there are any scm processes running, but there were none, so I believe when Jenkins invoke these commands there is only one scm process running at the time.

Thanks,
Ewa

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.