SAP Knowledge Base Article - Preview

2601423 - Max no of conversations exceeded using standalone JCo

Symptom

A problem occures while JCo client is trying to connect to the SAP Gateway using SAP JCo SDK. From client side a specific amount of max conversations are set. After an arbitrary count of transferred data, the following exception comes up in JCO<YYYYMMDD>_<time>.trc files:

This is caused by either a) an erroneous server configuration, b) the backend system has been shutdown, or c) network problems.
Failed to register JCoServer connection: Connect to SAP gateway failed
Connection parameters: PROGID=<>ProgId GWHOST=<hostname> GWSERV=<GWService> TRACE=1

ERROR max no of 600 conversations exceeded
TIME Wed Jan 13 06:59:48 2018
RELEASE 721
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 466
MODULE r3cpic.c
LINE 14641
COUNTER 95125

The connector trys to send the request but freezes. After some time a reboot is needed.


Read more...

Environment

  • Standalone JCo functioning as a client
  • NetWeaver Application Server

Product

SAP NetWeaver all versions

Keywords

JCO, Java Connector, -Djco.cpic_maxconv, Djco.cpic_maxconv, maxconv, max no of, conversations exceeded, Connect to SAP gateway failed, statefulm jco arcive, number, maximum , KBA , BC-MID-CON-JCO , Java-Connector , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.