Skip to Content
0
Former Member
Jul 25, 2007 at 09:17 AM

JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call.

100 Views

Hi

I am getting following exception while testing JCO connection

JCO Error: com.sap.mw.jco.JCO$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call.

Sometimes testing works file, Sometimes it gives above error.

From defaultTrace file , I got following information about error

Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed

Connect_PM TYPE=<> MSHOST=<serversid> GROUP=<group name> R3NAME=<R3 serveer sid> MSSERV=<> PCS=<>

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR max no of 100 conversations exceeded

TIME Tue Jul 21 11:29:19 2007

RELEASE 700

COMPONENT CPIC (TCP/IP) with Unicode

VERSION 3

RC 466

MODULE <>

LINE 10713

Till now I have found 2 solutions to the problem

1. Decrease connection timeout value for JCO parameter

2. Set CPIC_MAX_CONV=500

Now my qustions are:

1. Is there any other solution?

2. How to find whether problem is because of Insufficeient JCO connctions(Incorrect JCO connection setting) or because number of possible connections that R3 server allows has exceeded?

,i.e,whether error is because of R3 server setting or portal setting or anywhere else?

3.Where exactly CPIC_MAX_CONV value should be set and how?

4.Whether solution 1 or 2 is correct and will solve the problem?

5. Is there any blog which specifies how to handle this problem?

Thanks in advance,

Apurva