on 03-08-2007 7:01 AM
Hi all,
We encountered messages in SXMB_MONI with Error Category: RCVR_DETERMINATION and Error ID: CX_RD_PLSRV. Upon checking on the payload, the error messages are:
Sender Interface A
1) Problem while determining receivers using interface mapping: "COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection
2)Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found
3)Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. connection to partner '127.0.0.1:0' broken / CPIC-CALL:
Sender Interface B
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: "COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection</SAP:P1>
Initially, we thought that the system was down during those time frames which caused the JCo failure, but upon checking on the system, there was no history of system failure, and all the queues are working normally.
Are these errors really caused by JCo failure?Do we need to resend those messages? Or not resend those messages since no one is looking for them and we are not sure if they have resent them already?
Hope anyone could give insights to our problem.
Thanks in advance.
Hi Sreeram,
We are using Package com.sap.aii.mapping.*
Thanks,
Eric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sreeram,
We are using a DB Lookup in UDF...
Thanks.
Eric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhavesh,
Yes, you're right. We are using an enhanced receiver determination, and we found out that the reveiver in which the payload is populating is not included on the receivers configured on the user-defined function.
Thanks for your comment about JCo failure, this gave us a chance to check the performace of our server during those times.
Regards,
Eric
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sreeram,
Thanks for the reply. Actually, for Sender A, we found out that there is really a problem with the receiver determination. There is a missing field in the idoc being sent which is used to determine the receivers.
But, how come that it is connected to JCo failure?
Thanks again.
Hi Abhi,
Thanks for the link. I'll check it later.
Hi Venu,
I've tested the AI_DIRECTORY_JCOSERVER and AI_RUNTIME_JCOSERVER, and they are working fine.
Is it possible that even though there is a JCo failure on the error message, the whole XI system is not be affected, or there is no SYSFAIL in connection with J2EE engine?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Eric,
How are you determining your receivers?
are you using the Enhanced Receiver Determination using which a mapping determines the receiver?
If yes, then the mapping is not popualting the receiver and so, XI is erroring out with No receiver found.
As for the JCO failure, this can happen when the load on your server is high and most of the times, an automatic restart happens in XI itself.
I would suggest you look into the Mapping used to determine the receiver and check if the paylaod is actually populating the recievr as expected.
Regards
Bhavesh
Hi,
Is it possible that even though there is a JCo failure on the error message, the whole XI system is not be affected, or there is no SYSFAIL in connection with J2EE engine?
- If the problem in JCO failure your mapping and cache will get affacted or some JCO errors will appear.
Regards,
Venu.
hi,
go to Tcode : SM59 in your xi server
check the TCP/IP Connections which is created while post-installation phase..
1. AI_RUNTIME_JCOSERVER.
2. AI_DIRECTORY_JCOSERVER
check the above two connections are working properly or not.
Regards,
Venu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eric,
I am not sure about your problem as by checking the error it means there is no error in JCo Code , but you can go through this doc where you will know how to debug and analyze your errors in adapter engine.
This can help you out a bit.
Regards
Abhi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Eric,
your Reciverdetermination has some issues it could no find the correct Reciver or Interface which is your Interface mapping.
you want to process the same mesasge you need to resend it otherwise not required.
if they resent by some one you can check for sucessfully messages.
Regards
Sreeram.G.Reddy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.