Hello Micro Focus Team,

We are doing a transformation for one of the biggest client from Mainframe to Micro Focus AWS. We have different connectivity methods to support client's interface connection and these are

1. XMLG - running on EZASOKET

2. TN370

3. Stored Procedure

4. IIB Services - JDBC Connectivity.

We implemented the XMLG in our first phase of integration testing on EA server ( LINUX, Kubernetes) , and it was working fine since last 2 months. Last week we implemented few CICS Web Services in the container/ server and since then XMLG EZASOKET has stopped working. The CSKL listener is generating random errors 

230622 10241700       4504 CNDCICS  CASOP0000I 01 of 02 From (SYSAD,,CSKL) EZY1308E 06/22/23 10:24:13 ACCEPT CALL FAILURE TRANSACTION= CSKL  10
:24:13
230622 10241707       4504 CNDCICS  CASOP0000I 02 of 02 From (SYSAD,,CSKL) TASKID= 0019 ERRNO=    35

but it is still able to process the request via EZASOCKET. It may not be error , it is occurring right after CICS web Service has been invoked in server ( before that EZASOCKET was working fine). As soon as CWS are invoked by interfaces, EZASOCKET CSKL start failing with above error even when we have not received any EZASOCKET request. 

Next time when interface invokes the XMLG call using EZASOCKET , we are supposed to receive 3 events but Listener only picks 2 request and 3rd event give us socket read time out error. I read somewhere that SEP might be hanging the thread of CWS and can impact CSKL listening capacity. 

EZASOCKET is working perfectly fine without CWS in the Server. (As request from Interface is received by VPC at Port 12345, and then NLB put the request on random ports destined to end on the 67890 on CICS Server, we feared that NLB might be allocating the thread on already reserved ports and EZASOKET is behaving abnormally). Port 67890 is correctly reserved in our services in EZASOKET settinng.

Any idea on what is going wrong.