Resource ID appears to have a -1 for the agid

[RHPharr]

ODWEK 8.4.1.0

We have a bulk retrieval utility and have just made a change to only retrieve each resource file 1 time (by storing the file with the resource id and checking if we already have it).

During a run of 3300 docs, all of a sudden in the middle of the run, the resource ids appear to start showing -1 for the agid and it continues that way for the rest of the run.

Has anyone seen this? 

DEBUG~2013-05-22 13:20:48,968~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-20
DEBUG~2013-05-22 13:20:49,163~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-11
DEBUG~2013-05-22 13:20:49,108~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-68
DEBUG~2013-05-22 13:20:49,140~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-40
DEBUG~2013-05-22 13:20:49,314~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-50
DEBUG~2013-05-22 13:20:50,012~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-471
DEBUG~2013-05-22 13:20:50,032~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-21
DEBUG~2013-05-22 13:20:50,342~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-2
DEBUG~2013-05-22 13:20:50,783~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-254
DEBUG~2013-05-22 13:20:51,497~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net-13274-12
DEBUG~2013-05-22 13:20:52,027~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-128
DEBUG~2013-05-22 13:20:52,028~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-69
DEBUG~2013-05-22 13:20:52,030~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-65
DEBUG~2013-05-22 13:20:52,031~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-36
DEBUG~2013-05-22 13:20:52,032~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-336
DEBUG~2013-05-22 13:20:52,087~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-22
DEBUG~2013-05-22 13:20:52,214~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-212
DEBUG~2013-05-22 13:20:52,397~com.jpmc.ivault.deu.standalone.ODWekFileServer.run(73)~Resource id is cto6a098.svr.bankone.net--1-20

[Justin Derrick]

Nope, sounds like a bug.  Considering the version you're using, it seems very plausible, although I didn't see any fixes in later versions of 8.4.x that mention bad resources (you're using the Java API, right?)

I'd take another look at your code and make sure that it's not receiving something it's not expecting (like a string instead of an integer, prefixed spaces, or an error) and that the code is returning a -1 as an indication of a failure -- for example, that document doesn't have any resources associated with them, or that the resource is missing... 

Good luck!

-JD.

[Alessandro Perucchi]

Hello RHPharr,

:-) I will just say what the support will tell you... did you try to install the latest fix pack?
No? Then install and retry :-D

The problem is that version 8.4.1.0 (end of 2008, beginning 2009) is a really old version, and not supported anymore since September last year.
there have been 9 Fix Packs (latest one in Novembre 2012) ftp://service.software.ibm.com/software/ondemand/fixes/v841/

Normally by upgrading to the latest fix pack, there are no changes in the base installation, only bug fixes. So it shouldn't be a big changes.
If you use the ODWEK API, you will not need to recompile your code, just give the new ODApi.jar in the path, and relaunch it.

That should be it.

And when you can, please upgrade to 8.5 or 9.0.

Sincerely yours,
Alessandro