"lscm status" cmd is not displaying the output in cmd line
Accepted answer
Hi Mohan,
I found several similar questions on jazz.net regarding that:
https://jazz.net/forum/questions/100617/script-receives-failed-to-acquire-locks-on-requested-sandboxes-in-60000ms: Try setting the repository.timeout value in your preferences.properties file to a higher number. See:
https://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/index.jsp?topic=%2Fcom.ibm.team.scm.doc%2Ftopics%2Fr_scm_cli_preferences_properties.html
https://jazz.net/forum/questions/134315/what-is-the-basis-of-failed-to-acquire-locks-on-requested-sandboxes:
Let us know whether one it helps.
I found several similar questions on jazz.net regarding that:
https://jazz.net/forum/questions/100617/script-receives-failed-to-acquire-locks-on-requested-sandboxes-in-60000ms: Try setting the repository.timeout value in your preferences.properties file to a higher number. See:
https://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/index.jsp?topic=%2Fcom.ibm.team.scm.doc%2Ftopics%2Fr_scm_cli_preferences_properties.html
https://jazz.net/forum/questions/134315/what-is-the-basis-of-failed-to-acquire-locks-on-requested-sandboxes:
- Logout of any local sessions (lscm logout)
- Kill any running workspace daemons (scm daemon stop)
- Recycle my terminal session (start a new shell)
Let us know whether one it helps.
One other answer
Hi Mohan,
I would expect that this is correct behavior. As you have already created workspace, you should not have any changes there. Or I missed something?
You can try running also lscm status -v to confirm that lscm command works.
Let us know if that helps.
I would expect that this is correct behavior. As you have already created workspace, you should not have any changes there. Or I missed something?
You can try running also lscm status -v to confirm that lscm command works.
Let us know if that helps.
Comments