You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
@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.
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.
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
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! Failed to acquire exclusive lock on instance of '%IPM.Storage.ResourceReference'
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?
The text was updated successfully, but these errors were encountered: