8.5.2: Java agent using a script library causes "Invalid or nonexistent document"

Hi,

when we upgraded our server from 8.5.1FP4 to 8.5.2, a few (http started) java agents that use script libraries started giving error:

[HTTP Web Server: Lotus Notes Exception - Invalid or nonexistent document]

After that I have been able to create one working java agent that uses a java script library. All other times I’ve ended up getting the same error. The agent does not start at all, it gives this error immediately when started by URL. I’ve tried e.g. the following:

  • fixup and compact

  • tried in multiple databases

  • created agent and lib from scratch

  • created a new db, new empty lib and new empty agent, imported the lib to agent: starting this agent caused the server to crash!

My Designer version is also 8.5.2 (Win). This looks like a serious bug in 8.5.2: it is not possible to use java script libraries from java agents in most of the cases!

Anyone seen the same problem and found a solution?

thanks,

  • Panu

Subject: Same problem here

Hi Panu,

I have the same problem. Did you find any solutions to this?

-Kiarash

Subject: SPR & APAR

Hi,

these have been created by Lotus support:

SPR # DWHN8BCJ5U

APAR # LO56504

I haven’t tested yet with 8.5.2FP1.

  • Panu

Subject: Does not work in 8.5.2FP1

Tried using FP1 Designer and server and got the same problem immediately.

Subject: Fixed in 8.5.3!

http://www-10.lotus.com/ldd/r5fixlist.nsf/5c087391999d06e7852569280062619d/0b6d05c2aa76fc0385257814005d2374

Subject: copy classes from script library to agent

Hi PanuI have the same problem with one application after upgrading our server from 8.5.1FP4 to 8.5.2.

I couldn’t find a way to solve this, so I copied the classes from the script library directly to the default package of the agent and removed the script library from the agent. This is a rather poor workaround, especially if you have several agents accessing the same script library. Please post if you find a clever solution to this problem.

Subject: I have the same problem

Did anyone find a solution to this? Specifically this caused the a form’s webQuerySave agent to stop working.

I copied the classes out of the script library into the main agent, and it corrected the problem. Not an ideal solution since the script library was used extensively by other agents.

thanks