It's all about the answers!

Ask a question

Error Retrieving Images Using DNG REST API

Matt Green (1315) | asked Oct 11 '17, 4:12 p.m.

Currently I'm efforting to display Images in a DNG Export, but I'm experiencing issues retrieving the image using the REST API. 

I followed the response given,I'm trying to print a image by directly using dataSource/artifact/wrappedResourceURI, the image is not appearing. I tried putting the wrappedResourceImageURI in the browser with "?private=true&accept=" concatenated on to the end of the URI, 

Instead of a image, I received a 410 Response

I followed up on the thread, and I got the following response:

"Error 410: Gone" means the target image have been deleted in DNG. It appears the image uploaded to DNG, which was inserted to this artifact, has been deleted. Go to rm/admin --> debug --> Debug Service --> paste this wrappedResource URI, and GET to verify this URI.

Either way, it is more likely a DNG problem (DNG REST API problem). Submit the same question in if problem persists.

I really need help figuring out how to retrieve Images from DNG, and insert them into a document using a RPE template. If there is a better way than the method I listed above please let me know.

Donald Nong commented Oct 11 '17, 10:54 p.m.

I don't have RPE but the same method works for me in a browser. So I believe you need to figure out why you've got the HTTP 410 error.

Kenji Sarai commented Oct 12 '17, 10:03 p.m.

One possible cause is index. Old index might be pointing to invalid URI, and display http 410 error. You might try to regenerate indices, but unfortunately no guarantee. The root cause analysis should be done by DNG specialist.

Matt Green commented Oct 13 '17, 11:59 a.m.

 In absence of a DNG Specialist, what is the process of regenerating the indices? Documentation for this effort?

Some more questionsn:
  • Does index regeneration affect indices of all Streams? Or just one Stream? 
  • Regarding the cause of the issue, could be other causes for the 410 error?

Kenji Sarai commented Oct 15 '17, 11:51 p.m.

Here is how to re-generate the indices (repotools-rm). Make sure to stop the server and backup old indices. It will affect all resources.

Another possibility is that the server is under extreme pressure. It is difficult for me (and perhaps for anyone, given there is no other response so far) to nail down the cause. Please contact IBM support for detailed investigation.

Be the first one to answer this question!

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.