It's all about the answers!

Ask a question

how to determine why DNG import of a word doc stalled


Norman Dignard (354457100) | asked Jun 18 '15, 1:05 p.m.

We have noted a problem on our JAZZ testbed in importing work docs into DNG.  The import process just stalls on a number of import attempts and we appeared to fix the issue by restarting JAZZ which then allowed the user to import the document again.

In parralllel with this we noted that the disk space used for the JAZZ  indices was 100%.

Would this cause the import to stall?

 

Accepted answer


permanent link
Stef van Dijk (2.0k79) | answered Jul 18 '15, 10:37 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Certainly running out of disk space can be an issue because artifacts are actively being indexed during the import process.
That said, we have seen various issues with imports that can result in a stall. You could contact IBM Support to see if you are experiencing one of those issues which will likely require gathering more information than can be provided here. One obvious question is which version of DNG are you using?
Norman Dignard selected this answer as the correct answer

One other answer



permanent link
Howard Hsiao (5.4k7) | answered Jul 20 '15, 2:17 a.m.
JAZZ DEVELOPER
When you import, do you use keywords?

There is currently a keyword related issue with DNG
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=96665

It is scheduled to be fixed in 6.0.1.

Comments
Norman Dignard commented Jul 20 '15, 7:12 a.m.

No keywords were used. It appears that due to lack disk space for the indicies

may have been the culrupit. 

Your answer


Register or to post your answer.