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; } } }

Server did not accept open request

JohnL

We are getting this error "Server did not accept open request" on an intermittent basis. I'm using LAPI 9.1 java classes and connecting to an Livelink 9.1 server. I saw the posting about timeout problems related to DNS but I think this is a different issue. Here is the stack trace:com.opentext.api.LLIOException: Server did not accept open requestat com.opentext.api.LLConnectRouter.receiveOpenResponse(LLConnectRouter.java:82)at com.opentext.api.LLConnect.executeTraditional(LLConnect.java:1581)at com.opentext.api.LLConnect.execute(LLConnect.java:355)at com.opentext.api.LAPI_DOCUMENTS.DeleteObject(LAPI_DOCUMENTS.java:600)Roberto MongeVizdom Softwarermonge@vizdom.com

Find more posts tagged with

Comments

eLink User

Message from chris meyer via eLinkIt looks like a timeout of your session. Try this:Find the following in your opentext.ini file, and increase the timeout.This makes a Livelink a bit more patient with LAPI calls. Timeout ismeasured in ms.[sockserv]lib=.\bin\llsockserv.dllname=sockservgroup=sockserv.grpprio=criticaltimeout=5000A more robust solution is to catch the exception and reconstruct yoursession object. cheers, chris----- Original Message -----From: "eLink Discussion: LAPI Discussion" To: "eLink Recipient" Sent: Saturday, July 27, 2002 2:55 AMSubject: Server did not accept open request> Server did not accept open request> Posted by VIZDOMAdmin on 07/26/2002 08:54 PM>> We are getting this error "Server did not accept open request" on anintermittent basis. I'm using LAPI 9.1 java classes and connecting to anLivelink 9.1 server. I saw the posting about timeout problems related toDNS but I think this is a different issue.>>> Here is the stack trace:>> com.opentext.api.LLIOException: Server did not accept open request> atcom.opentext.api.LLConnectRouter.receiveOpenResponse(LLConnectRouter.java:82)> at com.opentext.api.LLConnect.executeTraditional(LLConnect.java:1581)> at com.opentext.api.LLConnect.execute(LLConnect.java:355)> at com.opentext.api.LAPI_DOCUMENTS.DeleteObject(LAPI_DOCUMENTS.java:600)>> Roberto Monge> Vizdom Software> rmonge@vizdom.com>> [To reply to this thread, use your normal e-mail reply function.]>> ============================================================>> Discussion: LAPI Discussion>https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=view>> Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe>>>

Chris_Wagg

Modifying timeout probably isn't the right way to handle this. instead, you want to modify acceptTimeout. The following Knowledge Base Article outlines how to use that setting. The article talks about Remote Cache, but the setting applies to any product that is trying to get a response back from Content Server and is timing out:

https://knowledge.opentext.com/knowledge/cs.dll/kcs/kbarticle/view/KB441138

Chris Wagg