2314297 - MAX NO OF 202 CONVERSATIONS EXCEEDED - Load Balancing - SAP Work Manager and others

• When the user tries to sync/transmit from SMP Work Manager Application, seeing the following error:
• ~~~~~~Error~~~~~~~
  MAX NO OF 202 CONVERSATIONS EXCEEDED
  ~~~~~~End~~~~~~~~
• Applied SAP notes # 2124330,2260950 by keeping

  -Djco.cpic_maxconv=1000

  JVM properties can be set in /MobilePlatform3/Server/props.ini in the #jvm section.

• Produces Error: User XXXXX (Masking real customer name) and companyName.messageserver.com (Masking real customer server name).
  

  ~~~~~~~~Start Here~~~~~~~~~~~~

  openCustomConnection::Failed to establish connection for user XXXXX: connection closed without message (CM_NO_DATA_RECEIVED) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########User::rethrowException::begin |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########User::rethrowException::Exception caught: Could not login user XXXXX - com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Initialization of destination custom_USER_AUTH_XXXXX failed |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.sap.conn.jco.rt.RfcDestination.initialize(RfcDestination.java:899) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.sap.conn.jco.rt.RfcDestination.ping(RfcDestination.java:1302) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.syclo.sap.jco.JCo3Connection.openCustomConnection(JCo3Connection.java:434) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.syclo.sap.auth.AbstractLoginModule.createClient(AbstractLoginModule.java:159) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.syclo.sap.auth.LoginModuleSSO.login(LoginModuleSSO.java:115) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at sun.reflect.GeneratedMethodAccessor206.invoke(Unknown Source) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at java.lang.reflect.Method.invoke(Method.java:606) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at javax.security.auth.login.LoginContext.invoke(LoginContext.java:784) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:203) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at javax.security.auth.login.LoginContext$5.run(LoginContext.java:721) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at javax.security.auth.login.LoginContext$5.run(LoginContext.java:719) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at java.security.AccessController.doPrivileged(Native Method) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:718) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at javax.security.auth.login.LoginContext.login(LoginContext.java:590) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.syclo.sap.User.handleJAASLogin(User.java:2615) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.syclo.sap.User.initSession(User.java:824) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########    at com.syclo.sap.Server.login(Server.java:484) |
  2016 05 05 12:38:25#+0100#INFO#System.out###Agentry Runtime Worker Thread########Caused by: com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: connection closed without message (CM_NO_DATA_RECEIVED) (remote system is <empty>|companyName.messageserver.com/00) |
  
  

  ~~~~~~~~~~~~~End~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

• USER_AUTH_SSO and GROUP_LOGON in javaBE.ini - connection closed without message (CM_NO_DATA_RECEIVED) 

• SAP Work Manager 6.1.0
• SAP Mobile Platform 3.0 SP08

"SMP 3.0 Agentry Loadbalance", "Load Balance Work Manager", "Load Balancing", "JAVABE.ini Loadbalancing", CM_NO_DATA_RECEIVED , KBA , MOB-SYC-SAP , Syclo Mobility for SAP backend , Problem