Connection gets down

Question

Hi everybody,
my client is experiencing a strange problem... he is trying to run a query.. but he gets no results at all. The query has been built on an infoset and gives info on 0Material and its attributes.. I've seen the layout designed by my client and I can say it is quite simple. There is only one filter on 0Material. It consist of a selection option variable. When he executes the query, if he inserts in the selection option only few values he is given the results eventhough with a big delay. If he inserts about 500 part numbers he doesn't get any result and furthermore BEx keeps displaying the message..."Wait for....bla bla bla".
I thought the problem could be that of filtering too many part numbers because of generating an oracle statement too big... but I tried with 2000 part number and also with the ones selected by my client and I got the results in few minutes.
While my client was running the query I checked the processes running with transaction SM50/SM51 and I noticed that there was no process running at all...I checked with transaction ST22 if there was any dump but no dump was generated.. I tried then to see if there were errors in transaction SM21..and I see this message:
Communication error, CPIC return code 020, SAP return code 223
ConversationID:52004099                                  
CPI-C function: CMSEND(SAP)
it says that code 223 means network read error...
does anybody know what it means?? Hope someone can help!!!!
Thanks in advance for your help
Regards,
Marco

Answer 1

The problem is for SAP System Administator:
1) He could maximize the number of conntection with the gateway to
support more parallel processes.
2) the second solution is written in OSS:
Temporary workaround:Set the gw/gw_disconnect parameter to 0. Connections are no longer broken, so terminations are no longer possible.
***The error is definitely eliminated at the following patch levels**** (devi far installare le seguenti patches):
620: 380
610: 610
46D: 1293
The function allowing connections between two gateways that have not been used for a long time to be closed is only available as of Kernel Release 46D. Therefore, corrections do not exist for lower kernel releases either.
Ciao,
C@f