Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
MBException: Cannot revise metadata on a locked asset.
JimD
Hi. I am getting exception: MBException: Cannot revise metadata on a locked asset.
-There is only 1 user using the system, and it is a user with whos name my program is running.
-This happends during this call:
cjob.getMyStub().reviseAssetMetadata(movedAssetID,(new ArrayOfMBMetadata(mergedAssetMetadata)));
-Just before this program runs, another program injest an external asset into MediaBin.
Thanks.
Jim.
Find more posts tagged with
Comments
Migrateduser
Hey Jim,
In our business we consume approximately 1500 new assets a day. We use the Publication Service (Hot Folders) to ingest the assets. One thing I have noticed is that when an asset comes into the system it's a multi-step process. I don't work for iwov, so I'll summarize what I *think* to be the process and I hope you find it helpful.
1. The asset goes to HotFolder
2. A job is created in the Active Job queue
3. The asset is ingested once it is at it's special time in the queue
4. (This is where it gets interesting)
5. The asset is checked out. (I *think* this is because metadata is being set on the image but, don't know for sure.)
6. The asset is checked back in.
So between step 5-6 there is a delay where an asset is checked out and locked. We have a backend tool that I created which picks up the assets and munges metadata and moves it to a different location. In our case perhaps once a week, a file is checked out and gets stuck like that. This process errors out because it can't move munge and move the asset which is how I have learned about this process. I manually go into the MBClient and unlock the file.
i think that the ingesting process is getting an error somewhere and fails to unlock the image during the process.
I hope you find this information helpful.
lyman
I can confirm that the server obtains a lock on your behalf before and after modifying metadata to help keep everything transactional. Large pieces of metadata have implications for the file system and so some external measures are required to keep everything consistent. However, inserting one asset should not affect revising metadata on another. Is it possible that there are two copies of your script trying to revise metadata on the same file?
This is the first time I recall anyone running in to this issue. If the problem persists please open a support case.
Cheers,
Lyman Hurd