Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to acquire exclusive lock on instance of '%IPM.Storage.ResourceReference' #717

Open
jinlouISC opened this issue Jan 24, 2025 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@jinlouISC
Copy link

IPM v0.10.0-beta.4

This occurred while loading an IPM module HealthShare.HP.PAS tarball into an I4H instance. Note: HealthConnect.Common is a dependency's dependency module.

`Loading file /Users/jlou/Perforce/jlou_workspace_2/projects/healthshare/appmodules/CMS-0057-WIP/HealthConnect.Common/latest/module.xml as xml
ERROR #5803: Failed to acquire exclusive lock on instance of '%IPM.Storage.ResourceReference'

ERROR #6315: Errors reporting importing XML subelement in file '/Users/jlou/Perforce/jlou_workspace_2/projects/healthshare/appmodules/CMS-0057-WIP/HealthConnect.Common/latest/module.xml' at line '2' offset '43', skipping this item.
Detected 1 errors during load.

ERROR! Failed to acquire exclusive lock on instance of '%IPM.Storage.ResourceReference'

ERROR #6315: Errors reporting importing XML subelement in file '/Users/jlou/Perforce/jlou_workspace_2/projects/healthshare/appmodules/CMS-0057-WIP/HealthConnect.Common/latest/module.xml' at line '2' offset '43', skipping this item.`

I was able to reproduce it on another I4H instance. The log suggests IPM failed to acquire a lock from another IPM process. Would anyone be able to provide any guidance?

@isc-kiyer
Copy link
Collaborator

@jinlouISC This is resolved by ensuring we set -DNoMapping=1 and load modules snychronously. Not sure which version of the ZHSLIB code you are using but @isc-jili is in the process of updating it to use the same build commands as the rest of the HS suite which ensure this error doesn't occur.

Long term, a vanilla install command should just work without needing such additional modifiers. However, that will only be resolved once there is some re-working of lifecycles.

cc @isc-tleavitt @isc-shuliu

@jinlouISC
Copy link
Author

This is not a build time issue but rather an issue loading tarball, so the fix mentioned above is not relevant. I checked in with @isc-kiyer and @isc-jili offline and did some further debugging. Eventually this is what worked for us:
zpm>load -DNoLock=1 -DNoTransaction=1 -DNoMapping=1

I am going to leave this issue open for the moment, in case IPM team would like to provide fix so that those modifiers are not needed.

cc @isc-tleavitt @isc-shuliu

@jinlouISC jinlouISC changed the title Question: Failed to acquire exclusive lock on instance of '%IPM.Storage.ResourceReference' Failed to acquire exclusive lock on instance of '%IPM.Storage.ResourceReference' Jan 28, 2025
@isc-shuliu isc-shuliu added the bug Something isn't working label Jan 29, 2025
@isc-shuliu isc-shuliu added this to the February 2025 milestone Jan 29, 2025
@isc-shuliu isc-shuliu added enhancement New feature or request and removed bug Something isn't working labels Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants