com.opentext.api.LLIOException Could not access server issue

hi, In our application we have installed Live Link enterprise server 9.7.1 in windows 16 CPU IBM X series m/c. Our application is java based. It uses LAPI to loging to LiveLink and gets a document from LiveLivelink. During our performance testing while the number of concurrent used is increased to more then 100 thread we are getting exception like hi, In our application we have installed Live Link enterprise server 9.7.1 in windows 16 CPU IBM X series m/c. Our application is java based. It uses LAPI to loging to LiveLink and gets a document from LiveLivelink. During our performance testing while the number of concurrent used is increased to more then 100 thread we are getting exception like com.opentext.api.LLIOException: Could not access server at com.opentext.api.LLConnect.createSocket(Unknown Source) at com.opentext.api.LLConnect.executeTraditional(Unknown Source) at com.opentext.api.LLConnect.execute(Unknown Source) at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)please help us.r at com.opentext.api.LLConnect.createSocket(Unknown Source) at com.opentext.api.LLConnect.executeTraditional(Unknown Source) at com.opentext.api.LLConnect.execute(Unknown Source) at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)please help us.

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

Hi Istiaque,

I suspect the following KB article is applicable to your situation:

https://knowledge.opentext.com/knowledge/livelink.exe/open/3500936

-chris

From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, July 29, 2009 12:53 AM
To: eLink Recipient
Subject: com.opentext.api.LLIOException Could not access server issue

com.opentext.api.LLIOException Could not access server issue

Posted by istiaque_hussain@infosys.com (Hussain, Istiaque ) on 2009/07/29 01:49

hi,
In our application we have installed Live Link enterprise server 9.7.1 in windows 16 CPU IBM X series m/c. Our application is java based. It uses LAPI to loging to LiveLink and gets a document from LiveLivelink. During our performance testing while the number of concurrent used is increased to more then 100 thread we are getting exception like
hi,
In our application we have installed Live Link enterprise server 9.7.1 in windows 16 CPU IBM X series m/c. Our application is java based. It uses LAPI to loging to LiveLink and gets a document from LiveLivelink. During our performance testing while the number of concurrent used is increased to more then 100 thread we are getting exception like
com.opentext.api.LLIOException: Could not access server
at com.opentext.api.LLConnect.createSocket(Unknown Source)
at com.opentext.api.LLConnect.executeTraditional(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)
please help us.r
at com.opentext.api.LLConnect.createSocket(Unknown Source)
at com.opentext.api.LLConnect.executeTraditional(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)
please help us.

Kevin_Bailey

Message from Kevin Bailey <kbailey@opentext.com> via eLink

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

I generally put a couple of retries in to get over the problem. This code snippet is for add version:

    // zealousCreateVersion
    //
    // If the client file system is very slow responding, the CreateVersion
    // call can fail because the server socket closes (it gives up waiting).
    // Optical jukeboxes can be slow when switching discs, for example.
    // To work around this particular problem, we retry a couple of times.
    // If it still isn't doing it, we give up and throw the LLIOException.
    // Otherwise we return the status of the version creation.

    private int zealousCreateVersion( int volumeID,
    int objectID,
    String path,
    LLValue versionInfo )
    {
        int status = - 1;
        int retries = 4;

        while( retries >= 0 )// Should be while(true)
        {
            try
            {
                status = llDocs.CreateVersion( volumeID,
                objectID,
                path,
                versionInfo );
                break;
            }
            catch( LLIOException e )
            {

                if( e.getMessage().startsWith( "Could not write bytes to socket" ) )
                {
                    if( retries > 0 )
                    {
                        System.err.println(
                        "Warning: Socket write error - retrying!" );
                        retries--;
                    }
                    else
                    status = - 1;
                    // Enough retries already!
                }
                else
                throw e;
                // Unhandled IO exception
            }
        }

return status;
}

From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, July 29, 2009 9:56 AM
To: eLink Recipient
Subject: RE com.opentext.api.LLIOException Could not access server issue

RE com.opentext.api.LLIOException Could not access server issue		Posted by cwebster (Webster, Chris) on 2009/07/29 09:56
In reply to: com.opentext.api.LLIOException Could not access server issue		Posted by istiaque_hussain@infosys.com (Hussain, Istiaque ) on 2009/07/29 01:49

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

Hi Istiaque, I suspect the following KB article is applicable to your situation: https://knowledge.opentext.com/knowledge/livelink.exe/open/3500936 -chris
From: eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, July 29, 2009 12:53 AM
To: eLink Recipient
Subject: com.opentext.api.LLIOException Could not access server issue

com.opentext.api.LLIOException Could not access server issue

Posted by istiaque_hussain@infosys.com (Hussain, Istiaque ) on 2009/07/29 01:49

hi,
In our application we have installed Live Link enterprise server 9.7.1 in windows 16 CPU IBM X series m/c. Our application is java based. It uses LAPI to loging to LiveLink and gets a document from LiveLivelink. During our performance testing while the number of concurrent used is increased to more then 100 thread we are getting exception like
hi,
In our application we have installed Live Link enterprise server 9.7.1 in windows 16 CPU IBM X series m/c. Our application is java based. It uses LAPI to loging to LiveLink and gets a document from LiveLivelink. During our performance testing while the number of concurrent used is increased to more then 100 thread we are getting exception like
com.opentext.api.LLIOException: Could not access server
at com.opentext.api.LLConnect.createSocket(Unknown Source)
at com.opentext.api.LLConnect.executeTraditional(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)
please help us.r
at com.opentext.api.LLConnect.createSocket(Unknown Source)
at com.opentext.api.LLConnect.executeTraditional(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)
please help us.

Christopher_Meyer

Message from Christopher Meyer <cmeyer@resonatekt.com> via eLink

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> A more generic approach can be found in the EasyLLSession class, whichis a part of the EasyLAPIpackage available on the KC.

All LAPI requests go through the Execute() method ofcom.opentext.api.LLSession. The EasyLAPI.EasyLLSession class extendsLLSession and overrides the Execute() method to catch any LLIOExceptionand retry the request after a short delay. The delay and number ofretries can be configured with the following static methods:

EasyLLSession.setExecuteAttempts( 5 );
EasyLLSession.setTimeBetweenAttempts( 5 ); // in seconds

Usage is very simple. Just use the EasyLAPI.EasyLLSession()constructor in place of com.opentext.api.LLSession() when creating yoursession. Although EasyLAPI.EasyLLSesion is part of the EasyLAPIpackage, it has no direct dependency on the package and can beextracted and used independently (just change the package declarationaccordingly).

eLink Discussion: LAPI Discussion wrote:

eLink

RERE com.opentext.api.LLIOException Could not access server issue Posted by kbailey (Bailey, Kevin) on2009/07/29 10:07
In reply to: REcom.opentext.api.LLIOException Could not access server issue Posted by cwebster(Webster, Chris) on 2009/07/29 09:56

Message from Kevin Bailey <kbailey@opentext.com>via eLink

Igenerally put a couple of retries in to get over the problem. This codesnippet is for add version:

   // zealousCreateVersion
    //
    // If the client file system is very slow responding, theCreateVersion
    // call can fail because the server socket closes (it gives upwaiting).
    // Optical jukeboxes can be slow when switching discs, for example.
    // To work around this particular problem, we retry a couple oftimes.
    // If it still isn't doing it, we give up and throw theLLIOException.
    // Otherwise we return the status of the version creation.

    privateint zealousCreateVersion( int volumeID,
    int objectID,
    String path,
    LLValue versionInfo )
    {
        int status = - 1;
        int retries = 4;

       while( retries >= 0 )// Should be while(true)
        {
            try
            {
                status = llDocs.CreateVersion( volumeID,
                objectID,
                path,
                versionInfo );
                break;
            }
            catch( LLIOException e )
            {

               if( e.getMessage().startsWith( "Could not write bytes to socket" ) )
                {
                    if( retries > 0 )
                    {
                        System.err.println(
                        "Warning: Socket write error - retrying!" );
                        retries--;
                    }
                    else
                    status = - 1;
                    // Enough retries already!
                }
                else
                throw e;
                // Unhandled IO exception
            }
        }

        return status;
    }

From:eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, July 29, 2009 9:56 AM
To: eLink Recipient
Subject: RE com.opentext.api.LLIOException Could notaccess server issue

REcom.opentext.api.LLIOException Could not access server issue Postedby cwebster(Webster, Chris) on 2009/07/29 09:56
Inreply to: com.opentext.api.LLIOExceptionCould not access server issue Posted by istiaque_hussain@infosys.com(Hussain, Istiaque ) on 2009/07/29 01:49

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

Hi Istiaque, I suspect the following KBarticle is applicable to your situation: https://knowledge.opentext.com/knowledge/livelink.exe/open/3500936 -chris
From:eLink Discussion: LAPI Discussion [mailto:lapi@elinkkc.opentext.com]
Sent: Wednesday, July 29, 2009 12:53 AM
To: eLink Recipient
Subject: com.opentext.api.LLIOException Could not accessserver issue

com.opentext.api.LLIOExceptionCould not access server issue Postedby istiaque_hussain@infosys.com(Hussain, Istiaque ) on 2009/07/29 01:49

hi,
In our application we have installed Live Link enterprise server 9.7.1in windows 16 CPU IBM X series m/c. Our application is java based. Ituses LAPI to loging to LiveLink and gets a document from LiveLivelink.During our performance testing while the number of concurrent used isincreased to more then 100 thread we are getting exception like
hi,
In our application we have installed Live Link enterprise server 9.7.1in windows 16 CPU IBM X series m/c. Our application is java based. Ituses LAPI to loging to LiveLink and gets a document from LiveLivelink.During our performance testing while the number of concurrent used isincreased to more then 100 thread we are getting exception like
com.opentext.api.LLIOException: Could not access server
at com.opentext.api.LLConnect.createSocket(Unknown Source)
at com.opentext.api.LLConnect.executeTraditional(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)
please help us.r
at com.opentext.api.LLConnect.createSocket(Unknown Source)
at com.opentext.api.LLConnect.executeTraditional(Unknown Source)
at com.opentext.api.LLConnect.execute(Unknown Source)
at com.opentext.api.LAPI_DOCUMENTS.ListObjects(Unknown Source)
please help us.

Carsten_Kulms

Message from Carsten Kulms via eLinkPlease note that LLIOExecption is very unspecific. The different causes can be distinguished (roughly) by the error messageonly. Examples are: Could not close socket Could not access server Could not open output stream [dynamic text] Could not create socket input stream. [dynamic text] Could not open input stream Could not write bytes to socket Could not flush socket Could not write inArgs to socket Could not write router packet to socket Could not read router packet from socket Server did not accept open request Could not create file: [dynamic text] Premature end-of-data on socket Could not write bytes to file: [dynamic text] Could not close file: [dynamic text] Could not access file: [dynamic text] Could not read bytes from file: [dynamic text] Could not close file: [dynamic text] Could not close file: [dynamic text] Could not open possible certificate fileNot in all cases it is worth or even reasonable to retry the call:LLIOException does not necessarily mean that the request did not makeits way to the server -- and is processed. Many LAPI calls are notidempotent.Also some LLIOException signal a client local problem, e.g. with fileaccess.Furthermore there are other LL...Exception likeLLCouldNotConnectException, LLCouldNotConnectHTTPException,LLBadServerCertificateException, LLHTTPAccessDeniedException,LLHTTPServerException (list is not complete). Some of these indicate aconnection problem that is worth a retry others signal a likelypermanent issue with the connection (or parameters, e.g. HTTPcredentials).