Recursive Code throwing "Server did not accept Open Request" errors

We have a long standing problem with the Livelink Recycle Bin module whereby autopurge fails to delete items because they are reserved or referenced by generations. How reserved items are ending up in the recycle bin I'm not sure (the module is supposed to have been fixed years ago to prevent this but it still happens) but that's not really the point.I have written a small program using LAPI to recursively search the recycle bin from the top down and check every item for reservation and/or references. The code runs fine, but intermittently it throws "Server did not accept open request" exceptions. Is there anything I can do to prevent this? I suspect the problem is caused by the large number of commands being thrown at the server over a relatively short period of time. I have considered introducing sleeps between method calls to mitigate this but I'm reluctant to make the code slower than it already is (it takes a while to trawl the whole recycle bin). Any ideas?

Find more posts tagged with

Comments

sıɹɥɔ

Message from Chris Webster <cwebster@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

There are two Knowledge Centre KB articles that might provide useful information for this issue:

https://knowledge.opentext.com/knowledge/llisapi.dll/open/3501616

and

https://knowledge.opentext.com/knowledge/llisapi.dll/open/3551156

-chris

From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, May 13, 2009 10:44 AM
To: eLink Recipient
Subject: Recursive Code throwing "Server did not accept Open Request" errors

Recursive Code throwing "Server did not accept Open Request" errors

Posted by natsadmin (Administrator, NATS) on 2009/05/13 11:33

We have a long standing problem with the Livelink Recycle Bin module whereby autopurge fails to delete items because they are reserved or referenced by generations. How reserved items are ending up in the recycle bin I'm not sure (the module is supposed to have been fixed years ago to prevent this but it still happens) but that's not really the point.

I have written a small program using LAPI to recursively search the recycle bin from the top down and check every item for reservation and/or references. The code runs fine, but intermittently it throws "Server did not accept open request" exceptions. Is there anything I can do to prevent this? I suspect the problem is caused by the large number of commands being thrown at the server over a relatively short period of time. I have considered introducing sleeps between method calls to mitigate this but I'm reluctant to make the code slower than it already is (it takes a while to trawl the whole recycle bin). Any ideas?

NATS_Support

Thanks Chris, I'll look into the solutions provided in those kb articles.