Bkmz написал:
ищи на sdn.sap.com, там много тем про эту ошибку есть...
Там такой же форум, как и здесь. Моя проблема не обсуждается. На MarketPlace нашлась только одна нота - 857846.
Symptom
When you call a function module implemented in Java, the client receives the message:
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:
connection closed without message (CM_NO_DATA_RECEIVED)
Other terms
JCO VMC JAVA function
Reason and Prerequisites
Due to an ABAP stack overflow on the application server side, the error message mentioned above occurs on the client side.
If you activate the work process traces (work process- trace level 2) on the application server on which the Java function was called, and you reproduce the error, you find a work process trace with an entry similar to the following:
A RFC ab_Rollout_Call_for_Java> wait rc = 0
Y Y
Y ======================== DYNP entry 12:
Y RollEnvir UNDEF 00092_00_0000000547 00 MACHTS
M ThGetRfcCliId2: got local client info from sysid >QPT <
M ThSetRfcCliAction: set action 1 > <
M ThGetRfcCliId2: got local client info from sysid >QPT <
M ThSetRfcCliAction: set action 3 >SAPMSSY1 <
Y Entry - COMMIT
Y ->PBO SAPMSSY1 3004 <> []
Y dynppbo0
Y ->(res) module %_RFC_START 8 prog >SAPMSSY1<
A SYSTEM-CALL RFC_END
---------------------------------------------------
trc file: "dev_w0", trc level: 2, release: "700"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 2
* ACTIVE TRACE COMPONENTS all, MYAJ
*
M Fri Jul 1 16:44:34 2005
M
If there are no more trace entries between "A SYSTEM-CALL RFC_END" and " ------------------------" (as is the case here), it is more likely that a stack overflow will occur.
We recommend that you search for "SYSTEM-CALL RFC_END" to find the relevant place quickly.
Solution
Import the following patch level:
SAP kernel release 700 patch level 13
Вход
Регистрация
FAQ пользователя
Поиск
