nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LAPI Time-out Errors

David_Forbes_(dforbes_-_(deleted))

Are there any reported cases of applications built using LAPI experiencing intermittent "time-out" problems, in large network environments?We have built a server based app, with LAPI, which calls Livelink. Both applications are resident on the same machine. In this environment, the LAPI calls may be routed through a DNS. Inconsistent results are being returned, based on the same source objects in Livelink.Any thoughts.... (help..!)David

Find more posts tagged with

Comments

Ketan_Mehta_(KMehta_(Delete)_787657)

Since you mentioned that you are developing a server based application where both your application as well as Livelink reside on the same machine, you may be able to connect using localhost to avoid a DNS lookup.

David_Forbes_(dforbes_-_(deleted))

We did eventually turn off the DNS services on the Livelink server (Win NT).This has solved the problem... sort of.Ryan advised us that LAPI will always try to use DNS services if enabled on the NT server. In our code we had specified an IP address...to no availDavid

x-opconuser3_-_(deleted)

In my LAPI experience, there are times when Livelink simply does not respond to a LAPI call.To counter this behavior, I wrap all LAPI calls with a loop with a retryCount and a retryDelay between retry attempts. Cumbersome, but effective.An example: int retryCount = 10; int retryDelay = 500; //milliseconds public void delete(int volumeId, int id) throws LLException {//System.out.println(this.getClass().getName() + ".delete("+volumeId+", "+id+")"); livelinkRequestAcknowledged = false; currentRetryCount = 0; while (! livelinkRequestAcknowledged && currentRetryCount < this.retryCount) { try { int i = this.llDocuments.DeleteObject(volumeId, id); livelinkRequestAcknowledged = true; if (i != 0) { throw new LLException(i,this.getSession()); } } catch (LLException e) { throw e; } catch (Exception e) { currentRetryCount++;//System.out.println(this.getClass().getName() + ".Livelink Acknowledgement Failed"); if (currentRetryCount == this.retryCount) throw new LLException(e.getMessage()); try {Thread.sleep(this.retryDelay);}catch(Exception exception) {} } } }

4-04-2014_5-06-24_AM.png

Alberto_Jimenez_Anguita

HiI'm developing a service to access LiveLink through LAPI and I was wondering if a call to LAPI could simply hang without returning, or it just returns an error after a timeout.Do you have any experiences on this issue?Thanks in advance

Tom__Turner_(BANONE02Admin_(Delete)_3045902)

Thanks for all the input.At least I know it is not just us with the issue.I am catching the exception and then going into a retry loop. Seems to work, but seems like there is something wrong "under-the-covers" that someone needs to look at.

Mario_Dzeba_(marshladmin_-_(deleted))

Dear eLinkCan anyone comment whether retryCount loop will work with .net???Many thanks for your comments