com.opentext.api.LLIOException

Tom__Turner_(BANONE02Admin_(Delete)_3045902)

Ocassionally, when processing quite a few items via LAPI (Java), we will randomly get a:com.opentext.api.LLIOException: Server did not accept open request.In the latest instance of this error this error occured once in about 15,000 operations where we were retrieving info from the server (ie no writes). The error occured after performing 72 successfull operations. any ideas ?Thanks

Find more posts tagged with

Comments

Jeremy_OConnor

Message from Jeremy O'Connor via eLinkTake a look at the following Knowledge Base Article it should help.https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3069744&objAction=ArticleViewJeremy-----Original Message-----From: eLink Discussion: LAPI Discussion[mailto:lapi@elinkkc.opentext.com]Sent: February 25, 2004 9:05 AMTo: eLink RecipientSubject: com.opentext.api.LLIOExceptioncom.opentext.api.LLIOExceptionPosted by Cole, Lindi on 02/25/2004 09:03 AMOcassionally, when processing quite a few items via LAPI (Java), we willrandomly get a:com.opentext.api.LLIOException: Server did not accept open request.In the latest instance of this error this error occured once in about 15,000operations where we were retrieving info from the server (ie no writes). Theerror occured after performing 72 successfull operations.any ideas ?Thanks[To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: LAPI Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

John_Shoun

We have seen the problem as well when running long transaction sessions or when using less reliable network connections -- the LAPI application will fail with the IO exception after running for a period of time.Our solution has been to use the HTTP option when connecting to the server instead of connecting directly to the server port (2099). This is described in the API documentation (and example would have been nice).We found that using HTTP increases connection reliability dramatically. I'm not sure what the complete explanation is, but it is a significant improvement.We still have code in Java to catch the IO exception and try to re-establish the connection before abandoning the application.

xybsir

what are all the impacts (good or bad) or things to be taken care of, when we connect to livelink server using HTTP protocol instead of TCP/IP protocol?